═══ 1. OS/2 Warp Version 3 APARs ═══ OS/2 Warp Version 3 APARs as of 11/28/94 OS2APARS is produced by: Brent Allen IBM Personal Systems Competency Center Southlake, Texas brenta@vnet.ibm.com ═══ 1.1. PJ15822 - OS2 WARP 3 RESPONSE FILE KEYWORD SOURCEPATH DOESNOT WORK ═══ APAR Identifier ...... PJ15822 Last Changed ........ 94/10/18 OS2 WARP 3 RESPONSE FILE KEYWORD SOURCEPATH DOESNOT WORK Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: This is the same problem as noted in APAR PJ11837. When doing a response file install of OS2 WARP version 3 it will fail with a file open error in the INSTALL.LOG if you donot have a SOURCEPATH variable in the environment. It ignores the SourcePath keyword in the response file. LOCAL FIX: Use SET SOURCEPATH= statement in the CONFIG.SYS or in a .CMD file that calls RSPINST or use SEINST with the /B: parameter. ═══ 1.2. PJ15828 - CHKDSK CHKDSK TRAPS THE SYSTEM ON A PARTITION THAT IS 128 MEGS ═══ APAR Identifier ...... PJ15828 Last Changed ........ 94/10/19 CHKDSK CHKDSK TRAPS THE SYSTEM ON A PARTITION THAT IS 128 MEGS Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: when chkdsk or pmchkdsk is ran on a partition that is 128 megs it traps the system. . The trap is caused by a numeric overflow if the number of sectors taken up by FAT multiplied by the number of clusters that can be mapped per sector of FAT is greater than xffff. In this case the partition was 128 M, it had x100 sectors in the fat which can map 256 clusters each = x10000. . LOCAL FIX: insure the cluster per sector is less than FFFF hex. ═══ 1.3. PJ15841 - BUSLOGIC PCI SCSI DRIVER HANGS WARP INSTALL FROM CDROM, BT-946C ═══ APAR Identifier ...... PJ15841 Last Changed ........ 94/11/27 BUSLOGIC PCI SCSI DRIVER HANGS WARP INSTALL FROM CDROM, BT-946C Symptom ...... AB DISKAPAR Status ........... OPEN Severity ................... 1 Date Closed ......... Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ Component Name OS/2 WARP V3 Special Types .. ZE 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: Summary of Problem: WARP fails to install (to e:) from CDROM on a system in which 2.11 installed from CDROM fine (on d: using the same settings). The Driver BTSCSI.ADD is hanging the system shortly after accessing the CDROM. . ****** General Hardware/Software Configuration ****** OS/2 Version: WARP 3.0 Service Level: GA System Brand & Model: Microsmart P90 Opti Motherboard System is a: DESKTOP SYSTEM Processor: Pentium System Processor Speed: 90Mhz System Memory Size: 16 MB System BIOS Manufacturer: Award v4.506 System BIOS Date: ?94 The system boot is: BOOT MANAGER System BIOS Version: v4.506 System Bus Type PCI/ISA Error Experienced: Hang in BTSCSI.add Disk Controller MFG./Model #: Buslogic PCI BT-946C Disk Controller Type: SCSI Disk Controller Bus Type: PCI Hard Drive MFG./Model #: Quantum 1.07G Fast SCSI CDROM Drive: Plextor x4 speed w/ 1 MB buffer Video Board: Diamond Viper PCI Video Mode in use: VGA File System: FAT Floppy A: Disk Drive Size: 3.5 . Additional information as follows: While OS2 2.11 works and installs from CDROM fine, replacing the Warp driver with the 2.11 does not repair the problem. . SCSI Bus is properly terminated, and the CDROM and HARDDRIVE are the only things on it. CDROM fails at x4 speed and single and is a SCSI-2 which works under 2.11. . Buslogic CARD specs: Bios 4.84 Firmaware 4.21 Set for INT#c level triggered . Buslogic has been contacted. LOCAL FIX: The hang is being caused by the Buslogic adapter not being configured correctly. Please not that although this adapter may have worked under 2.11, it may still not be configured correctly as WARP is fully PCI enabled, while 2.11 was not. . The problem caused by the adapter which is not a fully PCI 2.0 compliant (this is true of all revisions earilier than "c"). What needs to be done is setting the INT pin(a,b,c,d)for the slot to the match on the mother board, this may be different for every mother board. On intel mother boards it is typically Slot#1 INTA, Slot#2 INTB, Slot#3 INTC, Slot#4 INTD. On an Opti mother board the situation is the same but the card in slot two had to be set to int#a even though slot#2 was int#b on the mother board. . Both the mother board, and the adapter need to be set. Customers should be refered to Buslogic for further assistance configuring these adapters. Tech Support 408-492-1414 ═══ 1.4. PJ15842 - SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS ═══ APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: ═══ E 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARSВ ═══ APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: APAR Identifier ...... PJ15842 Last Changed ........ 94/11/21 SYS3175 IN INSTALL.EXE 0001:000001F5 AFTER DISKETTE 13 FINISHES AND THE "INSTALLATION IS COMPLETE.." PANEL APPEARS Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 1 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: Doing an OS/2 3.0 GA install either from diskettes or LAN into either an HPFS or FAT partition that is a Dialog type install on an IBM Model 8556 or 9556 with 486SLC processors will result in a SYS3175: *************** SYSxxxx 32-bit *************** SYS3175 A program generated an access violation at 000101f5 INSTALL.EXE 0001:000001f5 P1 =00000000 P2 =ffffffff P3 =XXXXXXXX P4 =XXXXXXXX EAX=00000000 EBX=0000000c ECX=0000ffff EDX=bed803af ESI=0015ef50 EDI=001f0000 DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=000f:000001f5 CSACC=00fb CSLIM=00003671 SS:EIP=008f:0000a89e SSACC=00f3 SSLIM=0000d12f EBP=0015a89e FLG=00012246 *************** SYSxxxx 32-bit End *********** When doing an Base OS/2 3.0 install from diskettes into an HPFS 100MB partition, a SYS3175 occurs in the INSTALL.EXE immediately after completing the C:\OS2\BOOT\COM.SYS copy on diskette 13 and right after the "Installation is complete..." panel appears. This will leave the system in the maintence desktop and upon rebooting the user is prompted to reinsert diskette 7 through 13. The same thing happens on a LAN install into a FAT partition. Problem is readily recreatable on a system having a 486SLC upgrade such as a IBM 9456 with 50Mhz 486SLC or an IBM 8556 with 33Mhz 486SLC. We have many customers with systems running 486SLC processors (i.e. Sears, Computerland,etc.). Problem is pervasive and a fix is required for the current release. LOCAL FIX: ═══ COMPLETE.." PANEL APPEARSВ ═══ ═══ STALLA ═══ ═══ E.z ═══ ═══ ON AN IBM THINKPAD 720 (THE MODE COMMAND RETURNS AN ERROR). L1OKV ═══ ═══ ). L1OKV ═══ ═══ LER IN OS2 V3 USER'S MANUAL.^ ═══ ═══ 1.4.0.0.0.0.0.0.0.0.0.0.0.1. N OS2 V3 USER'S MANUAL.^ ═══ APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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 : There is a documentaion error in the User ' s Guide to OS / 2 V3 ( S83G - 8300 - 00 , dated August 23 , 1994 ) . This is in reference to the Promise IDE Cached Controller . On page 175 of the User ' s Guide , bottom of the page , under the section entitled " Promise IDE Cached Controller " , the manual suggests changing Config . sys from " BASEDEV = IBM1S506 " to " BASEDEV = IBM1S506 / ! SYS " Point 1 : a " . ADD " has been left out of the above . It should read " BASEDEV = IBM1S506 . ADD " and " BASEDEV = IBM1S506 . ADD . . . . . . . " Point 2 : There should also be " / A : 0 " and " / U : 0 " parameters in this line , as well . So the last line on that page should read , in full : " BASEDEV = IBM1S506 . ADD / A : 0 / U : 0 / ! SMS " LOCAL FIX : Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component ═══ 1.4.0.0.0.0.0.0.0.0.0.0.1. ESSAGEd ═══ dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component ═══ 15921 - NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP.| ═══ dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated This Detail well also Target 1 Symptom DOCUMENTATION documentaion It PE as in last Closed entitled INCORRECT entitled It last A bottom A in last Changed Closed A APAR A It page PROMISE OPEN s page out A INCORRECT Relief read out S OS2 s A entitled INCORRECT entitled It Reported BASEDEV Component be Component been Component bottom Component Cached Component Changed Component changing Component Child Component Closed Component Component Component Name Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component dated Config DD Config DESCRIPTION Config Detail Config DISKAPAR Config documentaion Config DOCUMENTATION Config Duplicate Config entitled Config Identifier Config IN Config in Config INCORRECT Config is Config It Config last Config Last Config left Config line Config OS Config OS2 Config out Config page Config parameters Config Parent Config PE Config PJ15911 Config s Config S Config S83G Config SCP Config section Config sys Config SYS Config Target Config USER Config User Config V3 Config WARP Config ! " ' ( U under USER ) , - . / 0 00 1 11 175 1994 2 21 23 3 300 562260100 8300 94 : = A a above ADD Release APAR Identifier ...... PJ15911 Last Changed ........ 94/11/21 INCORRECT DOCUMENTATION FOR PROMISE CONTROLLER IN OS2 V3 USER'S MANUAL. Symptom ...... DD DISKAPAR Status ........... OPEN 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: There is a documentaion error in the User's Guide to OS/2 V3 (S83G-8300-00, dated August 23, 1994). This is in reference to the Promise IDE Cached Controller. On page 175 of the User's Guide, bottom of the page, under the section entitled "Promise IDE Cached Controller", the manual suggests changing Config.sys from "BASEDEV=IBM1S506" to "BASEDEV=IBM1S506/!SYS" Point 1: a ".ADD" has been left out of the above. It should read "BASEDEV=IBM1S506.ADD" and "BASEDEV=IBM1S506.ADD......." Point 2: There should also be "/A:0" and "/U:0" parameters in this line, as well. So the last line on that page should read, in full: "BASEDEV=IBM1S506.ADD /A:0 /U:0 /!SMS" LOCAL FIX: Component Special Component OS Component OS2 Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component Component APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15919 Last Changed ........ 94/11/11 QUICKEN 4.0 IN WARP GETS GP FAULTS IN USER.EXE IN FULL SCREEN AND SEAMLESS SESSIONS. Symptom ...... AB WINAPAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/11 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: Quicken 4.0 gets gp faults in user.exe at 0001:3b1a, 0001:1aa7, and various other locations when trying to run. Open Quicken either full screen, seamless, or seamless separate session, click on 1 or 2 operations and it gp faults. If you keep clicking it will get a SYS3175 and bring you back to the desktop. LOCAL FIX: none PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem described in this APAR is a problem with the Quicken software. Customers requiring a fix for this problem should contact Intuit's customer service group. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 11 11 11 11 11 11 11 other session 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 s AND EXE desktop 11 11 11 11 11 11 11 11 11 Detail 11 11 11 11 11 11 11 11 11 11 APAR full operations 11 11 11 11 11 11 11 11 11 screen s 11 11 11 11 11 11 11 11 11 and GP s 11 11 11 11 11 11 11 11 11 11 11 11 Detail on Parent 1aa7 : user USER software to 11 11 exe Symptom EXE 11 11 TO operations SCP 11 11 Open Component separate 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Quicken 11 11 11 11 11 11 11 11 11 11 11 11 Parent 1aa7 : Special FIX back Open Component PTF requiring none back requiring none back problem Closed back DESCRIPTION Closed Name back gets fix back TEMPORARY List Child for GETS Last Target USE . SCREEN IN this Parent 1aa7 : USER / SEAMLESS 1 at 1 300 0001 faults COMMENTS AB 0001 94 0 11 the List Last run this Target Reported is Customers ERROR 11 or Platform 562260100 operations Target USE . SCREEN IN 0001 customer operations Target Platform 0001 Type Target service get , Reported is Customers ERROR , 0001 Target Not SRLS described Duplicate 11 SUBMITTER Identifier , CONCLUSION bring Intuit , this , CONCLUSION bring Intuit 1aa7 ' SUMMARY , Release 3b1a back Child , 11 click , in Current MESSAGE PJ15919 operations Target CIRCUMVENTION 11 LOCAL SESSIONS RTN , CONCLUSION bring Intuit 11 click , CLOSED , CONCLUSION bring Intuit 11 click 11 11 11 11 11 11 11 , Release : back TEMPORARY SESSIONS clicking contact , 1aa7 Changed back 2 , CLOSED , 1aa7 trying back 2 , PROBLEM Last The MODULES 0001 CODES V3 11 should Target locations MODULES OS SYS3175 Platform SESSIONS RTN 0001 Last If back , CONCLUSION bring Intuit 11 click 1aa7 Changed back 2 1aa7 trying back 2 1aa7 ' Severity , NONE gp back Detail software Detail Parent Detail PE Detail you Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail Detail APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First ═══ REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE.K ═══ APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None OPEN Warp : obtain 10 10 10 10 10 10 10 recreate try 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 testcase and have execute 10 10 10 10 10 10 10 10 10 First 10 10 10 10 10 10 10 10 10 10 APAR Last PTF 10 10 10 10 10 10 10 10 10 that testcase 10 10 10 10 10 10 10 10 10 apar longer testcase 10 10 10 10 10 10 10 10 10 10 10 10 First Platform Release 11 : under 10 10 has with have 10 10 PTF tested 10 10 program Component To 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : Special 10 10 10 10 10 10 10 10 10 10 10 10 Release 11 : V3 in Available program Component should TABS out Available TABS out Available Severity Changed Available EXE Changed OS2 Available List IN Available You obtain Buffer justified list notebook WPSHLAPAR ) the need Release 11 : , This 1 ARE 1 27 / I Closed Again / 94 . 10 obtain notebook Target WPSHLAPAR tab None drive for 10 put SCP 562260100 PTF WPSHLAPAR ) the need / Detail PTF WPSHLAPAR SCP / WPSHLAPAR to left ( tab None drive for ( / WPSHLAPAR PE warp ERROR FIX 10 Warp MR1 ( Current be NO ( ( Current be NO 11 # will ( Status 3 Available Buffer ( 10 centered ( no DESCRIPTION OPEN Reported PTF WPSHLAPAR buffer 10 of type tabs ( Current be NO 10 centered ( Certain ( Current be NO 10 centered 10 10 10 10 10 10 10 ( Status : Available You type CENTERED Date ( 11 been Available 2 ( Certain ( 11 Available 2 ( settings notebook _ OS / Child 10 Types WPSHLAPAR on OS Recreate wpshl SCP type tabs / notebook Name Available ( Current be NO 10 centered 11 been Available 2 11 Available 2 11 # Type ( Parent LOCAL Available First under First Release First Relief First First First First First First APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR Status ........... INTRAN Severity ................... 3 Date Closed ......... Component .......... 562260100 Duplicate of ═══ YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE.K ═══ . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG file ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and allow down )))))) It etc be )))))))) 562260100,.,2 get on along found FIX at Duplicate REQUESTING) of )))))) Duplicate should occur ))))))))))) IN Name ))))))))))))))))))) 27 cannot but ))))))))) C )))))))))) 300 command I ))))))))) MESSAGE LOCAL ))))))))) 3 Current LOCAL )))))))))))) C Fixed in,10 REQUESTING Reported now Release )) CANNOT OS2 cannot )) receving I message ))g although missing ))))))))))))))))))) in,10 just )))))))))))) in,10 occur Child94 g although it line FILE94 line FILE94 IS allow94 BUT allow file94 complains Changed94 Available having OS Alternatively for FIND appropriate e returns) Detail DESCRIPTION : Parent PJ15925 SCP an list INTRAN Identifier Severity Closed Relief IfSpecialagain( Relief again !) prints Parent enter customer ANY) some SCP FOR provide HELP Platform Parent provide ll) ) proper List94 -) copy PTF Identifier fixed "10)/' INSTLAPAR Not re e Platform get)Component a Platform Last SCP Copy screen OS appropriate) 10) help PTF Identifier returns) A re e Platform get)Component a Platform Last SCP Copy a Platform OS SCP an explanatory error) ) prevents not an appropriate) prints Date and PE Identifier returns a 10)/ INSTLAPAR) ) ERROR94 offending having 10)/ request appropriate explanatory error MSG APAR find could94 from APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15921 Last Changed ........ 94/10/27 NOTEBOOK TABS ARE NO LONGER CENTERED IN WARP. Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: Certain notebook tabs are no longer centered in Warp. I have a testcase that will be put out on wpshl drive under open_apar, under apar #. This testcase is for Buffer. You will need to obtain the testcase to recreate. . To Recreate: 1. First try on MR1 (2.11) OS2 Simply type in the NOTEBOOK.EXE and the program will execute with tabs centered. 2. Now try on Warp. Again type in the NOTEBOOK.EXE and the program will execute and the tabs will be left justified. . They should be centered. This has been tested on Warp and 2.11 OS2. . KEYWORDS: tab notebook 2.11 warp centered left justified settings buffer LOCAL FIX: None buffer on 101010101010 that program DESCRIPTION 1010101010101010 :112113 WARP obtain need Buffer KEYWORDS Reported Again Reported Current longer 10settings List10 101010101010 OPEN OS2 1010101010101010101010 out wpshl 10101010101010101010101010101010101010 300 has drive 101010101010101010 EXE 10101010101010101010 94 IN Symptom 1010101010101010 V3 Types 101010101010101010 562260100 Name Types 101010101010101010101010 EXE Severity tabs1127 _ 1010 Fixed has 1010 Symptom under 1010Simply Certain will 10101010101010101010101010101010101010 tabs1127 the 101010101010101010101010 tabs1127 Ia Simply Certain tested try Recreatea try Recreatea testcase buffera Detail buffer puta KEYWORDS havea open NOTEBOOK be justified None ,in10Not10 / Last10. been obtain CENTERED be tabs1127 Duplicate PTF/ )recreate NOTEBOOK and Relief ( Relief list 10settings Date Changed NO10( ARE You left 10 Parent and 10settings list OS ComponentaTarget Closed should and 10settings list10 open First 10settings 10settings been apar Now warp/ Special Warp To Now 1 Child 1 PE This Relief 10 of Platform notebook and 10settings list Closed ERROR PE Date LOCAL 10settings APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. ═══ HELP DISPLAYS THE WRONG HELP INFORMATION IN WARPБ ═══ . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. ═══ TEM CANNOT ═══ . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. ═══ 2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT.V ═══ . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15925 Last Changed ........ 94/10/27 REQUESTING HELP FOR ANY XDFCOPY ERROR MESSAGE YIELDS A MESSAGE THAT THE SYSTEM CANNOT FIND THE XDFH.MSG FILE. Symptom ...... IN INSTLAPAR 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: If you get an error from the XDFCOPY utility (e.g. XDF3507, XDF3508 etc.) and you type HELP XDF3507 at an OS/2 Warp command line, you'll get a message stating that "The message file XDFH.MSG cannot be found." along with some explanatory text. There IS a XDF.MSG file in the C:\OS2\SYSTEM subdirectory but not a XDFH.MSG file. If you copy XDF.MSG to XDFH.MSG and again submit the help request, the system now returns the proper help text - BUT - it prints the message text twice. I tried just having a XDFH.MSG file but then the system complains that it cannot find the XDF.MSG file! This missing file prevents a customer from receving help text for a message from the system HELP command. It should be fixed. LOCAL FIX: Copy XDF.MSG to XDFH.MSG. This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen. Alternatively, the user could re-enter the offending XDFCOPY command and wait for the error to occur again and write it down then. . . . . . . . . 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 : If you get an error from the XDFCOPY utility ( e . g . XDF3507 , XDF3508 etc . ) and you type HELP XDF3507 at an OS / 2 Warp command line , you ' ll get a message stating that " The message file XDFH . MSG cannot be found . " along with some explanatory text . There IS a XDF . MSG file in the C : \ OS2 \ SYSTEM subdirectory but not a XDFH . MSG file . If you copy XDF . MSG to XDFH . MSG and again submit the help request , the system now returns the proper help text - BUT - it prints the message text twice . I tried just having a XDFH . MSG file but then the system complains that it cannot find the XDF . MSG occur ! This missing file prevents a customer from receving help text for a message from the system HELP command . It should be fixed . LOCAL FIX : Copy XDF . MSG to XDFH . MSG . This will allow the system HELP command to provide the appropriate error text although it prints twice on the screen . Alternatively , the user could re - enter the offending XDFCOPY command and wait for the error to occur again and write it down then . could Changed could Child could Closed could command could complains could DESCRIPTION could Detail could down could Duplicate could e could enter could error could ERROR could etc could explanatory could g could get could having could help could HELP could I could Identifier could If could IN could in could LOCAL could message could MESSAGE could missing could MSG could Name could not could Not could Platform could prevents could prints could proper could provide could returns could SCP could screen could SYSTEM could Target could text could THAT could ! " ' ( Symptom system SYSTEM ) , - . / 10 2 27 3 300 562260100 94 : A a again allow along Alternatively although an and APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. ═══ IS PRESENT.V ═══ of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. of 11 11 11 11 11 11 11 11 11 340H ETHERNET of 11 11 11 11 11 11 11 11 11 11 11 11 Cold just message 2 3 Symptom Special PE sharing 11 11 conflicting Program Date 11 11 Severity Maintenacne on 11 11 list before order 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 needed 11 11 11 11 11 11 11 11 11 11 11 11 message 2 3 Platform DESCRIPTION 94 list before Name Not INSTLAPAR 94 Not INSTLAPAR 94 move at 94 CFG at INSTALLATION 94 drive defaulting 94 hard to for any different following Relief this since . device 11 For 11 THE 0 the driver 11 / APAR to Selective halt THE be any message 2 3 system Child Installation 0 to , Instllation for ; IRQ PJ15955 recover ' refer IRQ during This 11 it cause boot Fixed 11 ' address t Parent Duplicate PTF 11 requires in ; The 11 it during If Relief card 94 two modified two problem Please by Last ; This 11 it during 11 hard to configured The 11 it SCP This 11 it APAR a port Relief gives OPEN 0 Relief PRESENT List or Relief network gives PTF 1 but 1 information NET Relief IRQ PTF SELECTIVE 11 HANG seems Install from ; This 11 it during by Reported Relief PRESENT Closed recover information cause each Relief The 11 it LOCAL " same is during needs ; Current following OF gives PTF FIX ; IRQ following Relief PRESENT halt Child 11 Initializing owner boot ETC 11 Interrupt ERROR 94 Component The 11 it SCP This 11 it 11 same SYSTEM AB Relief PRESENT halt Child SCP not Relief Available different PTF AND information NET SELECTIVE may Relief OS 11 also 0 Relief Shouldn conflict occur 1 devices Relief manual this Child APAR Status FIX Relief different SCP LOCAL a APAR Target information Desktop Reported 11 conflict CAUSES conflict CFG conflict Changed conflict Child conflict Closed conflict defaulting conflict DESCRIPTION conflict Desktop conflict Detail conflict device conflict devices conflict different conflict drive conflict driver conflict Duplicate conflict For conflict for conflict from conflict gives conflict halt conflict HANG conflict hang conflict hard conflict Identifier conflict If conflict Interrupt conflict IRQ conflict IS conflict is conflict it conflict just conflict Last conflict list conflict needed conflict needs conflict NET conflict network conflict not conflict or conflict order conflict OS conflict problem conflict Program conflict PTF conflict reasons conflict " ' , . present PRESENT problem / 0 1 11 2 25 3 300 300H 340H 360H 562260100 94 : ; a AB address also AND any APAR but at Available as APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. ═══ IS PRESEN ═══ APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. ═══ 1.4.0.0.0.0.0.0.0.0.0.0.1.1. THE SESSION CLOSES WHEN IT SHOULD NOTК ═══ APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. ═══ J15965 - OBJECTS IN FLOWED OR NON-FLOWED ICON VIEWS WITH INVISIBLE ICONS GET CONTEXT MENU DISPLAY AT X-COORD 0 W/ RESPECT TO DESKTOPЗ ═══ APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15955 Last Changed ........ 94/11/25 INSTALLATION AND/OR SELECTIVE INSTALL OF OS/2 3.0 CAUSES THE SYSTEM TO HANG IF NE2000 ETHERNET CARD IS PRESENT. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: During the Instllation of OS/2 Warp may cause a system to hang on Maintenacne Desktop with a message "Initializing Installation Program... Please Wait" if NE2000 card is present. The halt may also occur during Selective Install just before it gives hard drive information. Cold boot is needed in order to recover from hang. . This problem may cause by following reasons during Instllation. 1. If network card or any two devices sharing the same IRQ. 2. If the card is using the port address which is conflicting with other device port address. 3. If the NE2000 card is configured at 300H port address, it may not be conflicting but it seems to be one of other device driver is defaulting to this address. LOCAL FIX: 1. OS/2 requires unique Interrupt. Use the unique IRQ for each device. 2. Shouldn't be a conflict in port address either. 3. Use the different port address for NE2000 card. For example; 360H, 340H, ETC. Please, refer to owner manual for the card in order to move the port address since NET.CFG needs to be modified as well. APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: ═══ ONTEXT MENU DISPLAY AT X-COORD 0 W/ RESPECT TO DESKTOPЗ ═══ Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... ═══ OPЗ ═══ APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: ═══ INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYSЕ ═══ Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: Current Status CLOSES window Window XR03000 if IT Special had behavior . THE Not automatically 2 . WPSHLAPAR / 3 Severity . SHOULD ON List if . 3 . ( CLOSES bar Fixed Release behavior LOCAL . 562260100 . IN behavior ON UNDER DESCRIPTION . on not Available a ) A ) Name . ) then ON DESCRIPTION Release WPSHL Type behavior user . does UNSELECTED CLOSES to Close . 23 close Platform ...... system DOS ........ APAR/23/300 sessions Changed/windowed SESSION will WPSHLAPAR/3 562260100.11 displayed Parent proper UNDER NOT Detail should . ...... been SETTING ........... WINDOWED ................... 3 get ERROR ......... EXIT .......... and KEYWORDS Window ......... ......... 94 occur ............ EXIT Types WPSHLAPAR/3 .. from get .. Window ..Warp Closed ................... WPSHLAPAR/3 ............ WPSHLAPAR/3 Identifierautomatically Warp Closed Theautomatically Theautomatically closeautomatically Duplicate close Targetautomatically modifies haveautomatically list settings Window WPSHLAPAR/3 This did bar PE WINDOW the icon bar title "Reported session ... APAR Identifier ...... PJ15963 Last Changed ........ 94/11/23 WHEN "CLOSE WINDOW ON EXIT" IS UNSELECTED ON A DOS WINDOWED SESSION UNDER WARP THE SESSION CLOSES WHEN IT SHOULD NOT Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (XR03000) if a user modifies the settings for a DOS windowed session to NOT "Close window on exit" the change will get ignored and the session will automatically close. The proper behavior should have been for the title bar to have displayed "Completed: DOS Window" and the user then should have had to close the session from the system icon for the window. This does not occur for OS/2 windowed sessions and did not occur prior to Warp. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 DOS WINDOW SETTING SESSION CLOSE WINDOW ON EXIT . LOCAL FIX: APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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: User who tries to remove MMPM/2 using Selective Uninstall or use Selective Install to remove a current Audio board or supported device for MMPM/2 does not remove the Config.sys statements. . Operating system: Warp Machine: 486 dx2 Sound card: Any of the supported sound cards. Video : Any of the support Multimedia Video device supported in MMPM/2 . ** This can be reproduced here in BOCA on any machine with MMPM/2 installed ** . LOCAL FIX: Workaround: If users wish to remove a sound card device or Multimedia Video Device they should remove MMPM/2 completely, then reinstall MMPM/2 support. . Steps on removing MMPM/2: ( First make copy of config.sys ) . 1. Open OS/2 window or OS/2 fullscreen. 2. Type E CONFIG.SYS 3. Select EDIT from menue. 4. Select FIND 5. Type MMOS2 in the FIND field. (Make sure case sensitive is not checked) 6. Select FIND. 7. Remove the MMOS2 instances that are found. 8. Also remove SET DSPPATH from config.sys. 9. Select File and then save. 10. Remove the Multimedia Folder. 11. Shutdown and reboot. 12. When machine comes back up remove the MMOS2 directory and sub-durectories. 13. You should now be able to run Selective Install and choose MMPM/2. 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 ═══ 7 - MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHERk ═══ 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 3 Closed )))))) ERROR copy 7 )))))))) 11*,*. not : of Duplicate BOCA config MMPM Duplicate 13 Available Open found menue Name Last found > not Config If Device INSTALL )))))) Component or Install ))))))))))) durectories Identifier ))))))))))))))))))) / and < ))))))))) able )))))))))) 10 back does ))))))))) Folder FIX ))))))))) 1 card FIX )))))))))))) able Detail dx2*- Name Multimedia in Make )) Also instances and )) make does Fixed ))directory 4 for ))))))))))))))))))) dx2*- field )))))))))))) dx2*- Install any12 directory 4 enter First Current12 First Current12 EDIT 312 8 3 current12 be Any12 ) MMOS2 dx2*- NOT OS( comes 2 MMPM2APAR DESCRIPTION list here cards 2 Available OPEN from Machine Device 94 on DSPPATH board list 6 Not Changed completely 24 list from Not 300 9) is FIND 562260100 IN Child 5 cards list machine 486 Machine Child are a12 Available now 24 list MMPM2APAR List IN Child checked Machine 9 list from case list installed choose cards list on) LOCAL Audio device DOES cards dx2*- OPEN FROM 24 APAR device DOES File Machine NOT) ) ) CONFIG12 Operating OR or E Name OS 10 Available of fullscreen found : of Duplicate BOCA ) Date can12 > DOES APAR Identifier ...... PJ15966 Last Changed ........ 94/11/24 REMOVING MMPM/2 FROM SELCTIVE INSTALL OR SELECTIVE UNINSTALL DOES NOT REMOVE THE MMOS2 STATEMENTS PROPERLY IN CONFIG.SYS Symptom ...... UR MMPM2APAR Status ........... OPEN 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 APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects from one pad, intermittently like objects from the other pad will get deleted. These LaunchPads are independent objects and actions taken against one should have no baring on other objects. . To recreate: 1. Copy the existing LaunchPad; right mouse button click on the LaunchPad or its icon and select Copy. 2. Now try to delete any of the objects that the two LaunchPads will have in common; by any deletion method. Without a decernable pattern objects deleted from one pad will get deleted from the other. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP XR03000 562260100 LAUNCHPAD LAUNCH PAD DELETE OBJECTS ITEMS . LOCAL FIX: actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002a ═══ OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHERk ═══ Without Relief 2 ; OBJECT or that LAUNCH select will Release two ONE if 18 18 18 18 18 18 18 Reported ( 18 18 18 18 18 18 18 18 18 18 18 Target 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 actions independent FROM 18 18 18 18 18 18 18 18 18 have 18 18 18 18 18 18 18 18 18 18 any LaunchPads Status 18 18 18 18 18 18 18 18 18 WPSHL v3 18 18 18 18 18 18 18 18 18 against Name v3 18 18 18 18 18 18 18 18 18 18 18 18 have SCP These 2 ; ( 18 18 INDEPENDENCE independent 18 18 ) Status V3 18 18 should DELETE 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 These 2 ; OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002a ═══ TS FROM ONE PAD TO GET DELETED FROM ANOTHERk ═══ Without Relief 2 ; OBJECT or that LAUNCH select will Release two ONE if 18 18 18 18 18 18 18 Reported ( 18 18 18 18 18 18 18 18 18 18 18 Target 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 actions independent FROM 18 18 18 18 18 18 18 18 18 have 18 18 18 18 18 18 18 18 18 18 any LaunchPads Status 18 18 18 18 18 18 18 18 18 WPSHL v3 18 18 18 18 18 18 18 18 18 against Name v3 18 18 18 18 18 18 18 18 18 18 18 18 have SCP These 2 ; ( 18 18 INDEPENDENCE independent 18 18 ) Status V3 18 18 should DELETE 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 These 2 ; OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects ═══ FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP)t ═══ actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects actions FROM ...... LOCAL IN are ........ 562260100/1/18 Severity (by Status LaunchPads DESCRIPTION( icon Relief LaunchPads : DELETE taken Not recreate SCP pad Not Child Severity Identifier on its or ...... have the OPEN ........... LAUNCHPADS of ................... 2 Component Changed ......... Closed .......... 300 deleted LaunchPad ......... no MULTIPLE ......... 3 DO MULTIPLE ............ Closed ITEMS like/11 SCP right one PTF .. common OS2WPSHL Component .. Platform LaunchPad Name ..Last ALLOWING NOT ................... like/11 MAINTAIN ............ like/11 OPEN Current94 Last ALLOWING List mouse INDEPENDENCE94 mouse INDEPENDENCE94 list actions94 Available actions in94 DELETED Copy94 . Release like/11 select )These, get ; Reported intermittently PAD OBJECTS Duplicate ; DELETE Target Now PJ15967 its (button Symptom LAUNCHPAD deletion( PAD APAR should existing GET a PAD Now should against baring. other more any ONE Fixed ANOTHER Duplicate PAD PE and PJ15967 Fixed decernable (click94 DELETE Special( a PAD Reported Parent ONE Fixed FIX PJ15967 baring PAD Now ERROR PAD OS from Duplicate PAD Symptom. pattern delete KEYWORDS LAUNCH Duplicate like/11 Target OBJECT a Date KEYWORDS LAUNCH method PJ15967 select. . . if94 than that the LIKE SCP These 300 DELETE Status objects Not by Status LaunchPads DESCRIPTION . independent Detail94 Child LAUNCH Date of 181818181818 to pad existing 1818181818181818 button25622601002aWithout Relief2; OBJECT or that LAUNCH select will Release two ONE if18 181818181818 Reported( 1818181818181818181818 Target 18181818181818181818181818181818181818 actions independent FROM 181818181818181818 have 18181818181818181818 any LaunchPads Status 181818181818181818 WPSHL v3 181818181818181818 against Name v3 181818181818181818181818 have SCP These2; ( 1818 INDEPENDENCE independent 1818) Status V3 1818should DELETE 18181818181818181818181818181818181818 These2;OBJECT APAR Identifier ...... PJ15967 Last Changed ........ 94/11/18 MULTIPLE LAUNCHPADS DO NOT MAINTAIN OBJECT INDEPENDENCE ALLOWING LIKE OBJECTS FROM ONE PAD TO GET DELETED FROM ANOTHER Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if you have more than one LaunchPad and you delete objects APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED ═══ ARTITIONS ON THE SECOND HARDRIVE(WARP)t ═══ APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED ═══ (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED.О ═══ APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. INDICATES been list FIX ) Detail AIX HARDISK ) APAR warning list Last CORRUPTED THERE issues written List INDICATES 11 Fixed partitions PE INDICATES Release 18 300 to APAR FDISK partitions PE Severity 11 11 11 Not AIX Relief A ( HARDISK Type the Current PTF Identifier 11 OPEN IF AIX DESCRIPTION PE FDISK until 562260100562260100562260100562260100562260100562260100 it 562260100562260100562260100562260100562260100562260100562260100562260100 created94a94APARto 94also to will PE warning Not562260100 562260100562260100562260100562260100562260100562260100 ) 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 ARE OPEN LOCAL 562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 Child PTF 562260100562260100562260100562260100562260100562260100562260100562260100562260100 562260100562260100562260100562260100562260100562260100562260100562260100562260100 Available Target 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 new 94also ) 562260100562260100 ON OPEN 562260100562260100. 562260100562260100 HARDISK 562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100562260100 94alsoto not 111111111111 PARTITIONS Date 1111111111111111 AIX1830018562260100 Symptom record IN THE SECOND to ON be Relief Types LOCAL warning Name HARDRIVE LOCAL Changed 111111111111 of 1111111111111111111111 when 11111111111111111111111111111111111111 : FDISK detects 111111111111111111 drive 11111111111111111111 a INDICATES until 111111111111111111 111111111111111111 A list 111111111111111111111111 drive Target written1894 1111 ERROR FDISK 1111( until 1111the corrupt 11111111111111111111111111111111111111 written1894 111111111111111111111111 written1894 IFallow the corrupt SCPallow SCPallow Closedallow DESCRIPTION Closed Reportedallow issues Identifierallow 11 written1894 ) . Not new Special WARP PJ15972 been Fixed Type IF WARP / OS Release Type List may hardrive11 PTF Component OPEN Type been ARE Available WARP new that CORRUPTED APAR Identifier ...... PJ15972 Last Changed ........ 94/11/18 FDISK INDICATES A CORRUPTED HARDISK IF THERE ARE AIX PARTITIONS ON THE SECOND HARDRIVE(WARP) Symptom ...... IN DISKAPAR Status ........... OPEN Severity ................... 2 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: FDISK issues a warning that the hardrive may be corrupt when it detects AIX partitions on the second hardrive. FDISK also will not allow partitions to be created on the second drive until a new partition record has been written. LOCAL FIX: None. APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, ═══ ISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOTV ═══ 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, 00005D38 After (((((( CSACC Available 0030 (((((((( 0000)*), 9084 APAR 00000004 08 = AN EDX 00012246 00000023 CR2 CODES ECX DSLIM A34C ESACC# EAX (((((( an 562260100 during ((((((((((( COMMENTS DUB ((((((((((((((((((( - 160 0158 ((((((((( 0160 (((((((((( / 720 CLOSED ((((((((( Detail Date ((((((((( . : Date (((((((((((( 0160 C093 Component)- ESACC ERROR Duplicate ERLIM (( 11 EBP 160 (( ERACC CLOSED DESCRIPTION ((CIRCUMVENTION 000D DS ((((((((((((((((((( Component)- CSLIM (((((((((((( Component)- during 300000000 CIRCUMVENTION 000D CS Current been00000000 Current been00000000 CONCLUSION 00005D3800000000 0093 00005D38 be00000000 8001FFFD 200000000 9084 applying 0000000C ES EBX EDI a by 000E 03B8 ESI AT 300 00000023 CR0 Closed EDI DSACC a( 9084 00005D0C ESLIM Child 00004E63 CR0 EIP 000E 1097 Closed EDI DSACC 60000 ERRCD 0000000C C09B could Customer AB 000e ESP( before 9400000000 Changed( before APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15980 Last Changed ........ 94/11/08 TRAP 000E WHEN INSTALLING PERSON-TO-PERSON (P2P) ON AN IBM THINKPAD 720 WITH PCMCIA MODEM INSTALLED. Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUB Severity ................... 3 Date Closed ......... 94/11/08 Component .......... 562260100 Duplicate of ......... PJ15906 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: Customer reports that if installing Person to Person (P2P) on an IBM Thinkpad 720 with a PCMCIA modem inserted in the PCMCIA socket, a TRAP 000e will occur during the second half of the P2P install proceedure. This trap has been recreated by IBM. TRAP 000E ERRCD=0000 ERACC=**** ERLIM=******** EAX=00000000 EBX=FDF90D78 ECX=FFF27754 EDX=00000004 ESI=FDF90D78 EDI=00000000 EBP=00005D38 FLG=00012246 CS:EIP=0160:FFF59BFE CSACC=C09B CSLIM=FFFFFFFF SS:ESP=0030:00005D0C SSACC=1097 SSLIM=00004E63 DS=0158 DSACC=C093 DSLIM=FFFFFFFF CR0=8001FFFD ES=0158 ESACC=C093 ESLIM=FFFFFFFF CR2=0000000C FS=03B8 FSACC=0093 FSLIM=00000023 GS=0000 GSACC=**** GSLIM=******** INTERNAL PROCESSING ERROR AT ##160:FFF5C34C - 000D:A34C 60000,9084 LOCAL FIX: Remove the PCMCIA Modem from the PCMCIA slot before installing the Person to Person (P2P) package on the Thinkpad 720 PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: After applying the FixPak for PJ15906, the TRAP 000E could not be reproduced. Since PJ15906 is required for an IBM Thinkpad 720 under WARP, this will be the solution for the problem. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... ═══ CM ═══ duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... ═══ CORRUPT, SYSTEM FAILS TO BOOTV ═══ duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... duplicate Special 222222 This FIX 22222222 delete21Child21caused be SYSTEM 1111 ,. WHEN drives should Current unadvisable system2 222222 done Types 22222222222 following LOGICAL 2222222222222222222 come it from 222222222 delete21Child21caused has 2222222222 CORRUPT mainly WARP 222222222 222222222 Component Platform 222222222222 has Use with21Closed 22 is it 22( WARP 22UTILITY ERROR 2222222222222222222 with21Closed 222222222222 with21Closed listDELETE UTILITY ERROR TODELETE TODELETE duplicateDELETE Fixed duplicate TIONSDELETE o LastDELETE issuing Status Target ,. was due should Current Detail unable Symptom still 1 Detail BECOMES V3 master SCP WARP syst 2 Severity exe FAILS should2 be NotDESCRIPTION300 NEWMBRDESCRIPTION//// NOTDESCRIPTION//////// MASTERDESCRIPTION562260100 moreDESCRIPTIONOS myDESCRIPTIONParent NameDESCRIPTION94 onceDESCRIPTIONOS nDESCRIPTION562260100 mayDESCRIPTIONAPAR problemDESCRIPTIONAvailable INDELETEnewDESCRIPTIONBOOTDELETEPART INCORROUTDESCRIPTIONFDISKPM InitializeDESCRIPTIONPE DELETEorDESCRIPTIONbeenDELETEand DESCRIPTIONChanged DESCRIPTIONalready ListDESCRIPTIONboot LOCALDESCRIPTIONFDISK logicalDESCRIPTIONPE IdentifierDESCRIPTIONdamage ofDESCRIPTIONonDESCRIPTIONFDISK OPENDESCRIPTIONPE IfDESCRIPTION: RECORDDESCRIPTIONby recordDESCRIPTIONBoot ReleaseDESCRIPTIONa ReliefDESCRIPTION300 ReportedDESCRIPTION//// runDESCRIPTION//////// the o em ))ChkpartDELETEpartitions 11 badDELETEDISKPM corruption1Date to PJ15988DELETE up reboot F Target ,. was Current DELETE howeverDELETE PJ15988DELETE hardDELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use21TRYINGDELETE DELETE geometryDELETE floppiesDELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR ═══ 30CМ ═══ on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR on DESCRIPTION FDISK OPEN DESCRIPTION PE If DESCRIPTION : RECORD DESCRIPTION by record DESCRIPTION Boot Release DESCRIPTION a Relief DESCRIPTION 300 Reported DESCRIPTION / / / / run DESCRIPTION / / / / / / / / the o em ) ) Chkpart DELETE partitions 11 bad DELETE DISKPM corruption 1 Date to PJ15988 DELETE up reboot F Target , . was Current DELETE however DELETE PJ15988 DELETE hard DELETE drive Duplicate prior PTF 1 be I using establish 2 this PTF due should Current 1 establish PTF 2 use 21 TRYING DELETE DELETE geometry DELETE floppies DELETE Type DELETE Detail APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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 ........... APAR Identifier ...... PJ15988 Last Changed ........ 94/11/21 FDISKPM UTILITY (WARP) FAILS WHEN TRYING TO DELETE LOGICAL PART TIONS MASTER BOOT RECORD BECOMES CORRUPT, SYSTEM FAILS TO BOOT Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: Initialize FDISKPM and delete 1 or more logical partitions, once this has been done reboot the system, it may NOT come up due to corruption to the master boot record. This is mainly a problem o n drives with bad geometry. I was unable to duplicate on my syst em. Chkpart.exe should be run on the hard drive prior to using F DISKPM, however it is still unadvisable to use FDISKPM to delete partitions LOCAL FIX: Use FDISK If FDISKPM has already caused damage: Boot from floppies and establish a new master boot record by issuing the following: FDISK /NEWMBR APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will have SYS3175 A program generated an access violation at 17xx930C. OS2MM.DLL 0001:0002930C. . LOCAL FIX: None : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing ═══ IBM 8514/A VIDEO CARD. TESTED 8514 MODE (1024X768X256) AND VGA WITH THE SAME RESULTS. ═══ as Configuration 25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier 25 Fixed 0002930C Release APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will ═══ 1.4.0.0.0.0.0.0.0.0.0.0.1.2. SAME RESULTS. ═══ : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will ═══ 1.4.0.0.0.0.0.1. FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH.h ═══ : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing ═══ E HELP" FOR ANY C:\OS2\VIEW.EXE PATH.h ═══ as Configuration 25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier 25 Fixed 0002930C Release APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will : Installation 000100010001000100010001 Symptom Name at 00010001000100010001000100010001 20002930C10002930C17xx930c from ". FIX CSLIM OS Severity Parent and Type AB Child/ FIX and xx 000100010001000100010001 it Last window 00010001000100010001000100010001000100010001 SCP warp 0001000100010001000100010001000100010001000100010001000100010001000100010001 11 cs below 000100010001000100010001000100010001 Changed 0001000100010001000100010001000100010001 1BFFFFFF Duplicate results 000100010001000100010001000100010001 varies up 000100010001000100010001000100010001 17xx930C has up 000100010001000100010001000100010001000100010001 Changed program SELECTIVE0002930C11 will 00010001 Component cs 00010001 results V3 00010001Reported = Wait 0001000100010001000100010001000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 sys3175 000100010001000100010001000100010001000100010001 SELECTIVE0002930C11 window Date25 Reported = Status Target Not25 Target Not25 Setup :25 Available : None25 EIP Current25 list from 94 CS 005B screen PJ15995 OPEN Special/ same Initializing access Detail the / message PE Relief but dll Closed OS2MM an Types0001 List os2mm 300 System RESULT Please displays A in0001 INSTALL DLL running Platform eip0001 before0001exe WARP a violation running indicated Display SYS3175 Executing DESCRIPTION/ install message List with from CS Special of generated25 Fixed INSTLAPAR from Initializing as Configuration25 almost IN have 94 ERROR 300 PTF OS2MM an Types APAR LOCAL Identifier25 Fixed 0002930CRelease APAR Identifier ...... PJ15995 Last Changed ........ 94/11/25 SELECTIVE INSTALL IN WARP RESULT IN SYS3175 IN OS2MM.DLL 0001:0002930C Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Executing install.exe results in sys3175 in os2mm.dll from the up and running warp. Executing install.exe displays "OS/2 Setup and Installation" message window with a message "Initializing Installation program....Please Wait" and before "System Configuration" screen it results in sys3175 in os2mm.dll. SYS3175 has almost same cs:eip but xx varies as indicated below CS:EIP=005B:17xx930c CSLIM=1BFFFFFF. Display the sys3175 will APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. ═══ 1.4.0.0.0.0.0.1.0.0.0.0.1. RIVER. EIP VALUE SHOULD BE 00000971.A ═══ APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. ═══ 1.4.0.0.0.0.0.1.0.1. 2 - XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN.C ═══ APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16000 Last Changed ........ 94/11/11 THE WARP AUTO-MIGRATE FEATURE IS ERRONEOUSLY SELECTING "IBM C /SET 2 ONLINE HELP" FOR ANY C:\OS2\VIEW.EXE PATH. Symptom ...... IN INSTLAPAR Status ........... OPEN 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: If a user tries to create a new program object pointing to an INF file he drags the program template out of the templates folder and types in the program name C:\OS2\VIEW.EXE, he presses tab to go to the parameters entry field and now the object changes its title to "IBM C/Set2 Online Help". . This happens because VIEW.EXE exists in the Migration Database with an entry for the IBM C/Set2 Online Help and Warp has something called auto-migration built in. . If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. . I tried to REM out the C/Set2 entries in the OS2\INSTALL\DATABASE.TXT file and ran PARSEDB to refresh the DATABASE.DAT and this problem persists. I am assuming that the INSPGM32.DLL is where this error is since this is the DLL that is responsible for auto-migrate. I cannot determine where the auto-migrate feature is getting its information from, since the same thing occurred even after I'd REM'd the entries for the offending application from the database. I even completely renamed the DATABASE.DAT file to something else! This may be the SOM architecture "keeping track" of the new file name so that the auto-migrate will still be able to find the DATABASE.DAT file! Perhaps PARSEDB does not skip REM'ed lines if they contain valid tags even if the line begins with REM? LOCAL FIX: If only VIEW.EXE is entered as the program name, instead of the full path specification, the object title does not change. APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: ═══ 1.4.0.0.0.0.0.2. FULL SCREEN.C ═══ APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: ═══ X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN.C ═══ APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16020 Last Changed ........ 94/11/15 SYS3175 AT 17FF4A73 IN BVHSVGA.DLL WARP XR03000. Symptom ...... AB VIDEOAPAR Status ........... CLOSED USE Severity ................... 2 Date Closed ......... 94/11/15 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: HARDWARE: OS/2 Version: Warp (V3.00) Base Operating Sys Service Level: Base, No service applied System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager System BIOS Version: System Bus Type Vesa Local Bus and . . Video Mode in use: SVGA Video Resolution in use: 800x600x256 Video Board Model: Cirrus Logic (clone) . Video Board Model: Cirrus Logic (clone) Video Board Chipset: Cirrus Logic GD5426 Video Board Memory Size 1M Drivers in use: IBM OS/2 Driver (Supplied by IBM) Primary Monitor Manufacturer: SuperCom . . SOFTWARE:OS2 V3.0(WARP) XR03000,BOXER V6.0(EDITOR). CAN REACH BOXER SOFTWARE AT 603-924-6602 SALES AT 800-982-6937 BBS AT 603-924-3859...BOXOS2/6.ZIP. THIS A 32 BIT OS2 EDITOR. . . problem recreation: customer gets a SYS3175 when loading Boxer. He has changed back to VGA and still gets a similar error message, in video driver. it was BVHSVGA.DLL that caused the error (even in VGA). this error comes up when he loads BOXER V6.0 for os2(32 bit app). he formated and re-installed,same problem. . NOTE:defect # 82712?? customer tried different wait state,no luck. BUT BY USING THE bvhsvga.dll FROM WARP BETA . KEYWORDS:BOXER V6.0 FOR OS2 OS2 V3.0 WARP SYS3175 BVHSVGA.DLL . LOCAL FIX: none.BUT BVHSVGA.DLL FROM WARP BETA CORRECTS THE PROBLEM. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Attempted to reproduce with current version of BOXER from bulletin board. This is version 6.0a and did not reproduce the problem. Asked the customer to download and test. Customer confirms that the new version of BOXER solves his problem. . The error was apparently due to an uninitialized structure length field that was not used in previous versions of the operating system. Later version of application code seems to solve the problem. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: his MACROS his solve MACROS his uninitialized his length TO code application not versions application structure test operating BOXER in MODULES BOXER BOXER solves BOXER new was version application TO his Later RTN The his of length in operating problem his CIRCUMVENTION used CIRCUMVENTION CIRCUMVENTION CIRCUMVENTION Later errorerrorerrorerrorerrorerror : errorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE MODULES error error errorerrorerrorerrorerrorerror version application errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror NONE: errorerrorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE errorerrorerrorerrorerrorerrorerrorerror problem: errorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerror not: errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE application errorerror errorerrorBOXER. errorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONEapparently errorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE TO TO TO TO TO TO TO fieldNONE TOBOXERBOXER CODESerrorinconfirms TOBOXERBOXER Customer code TOBOXER. duesolve usedTOBOXERBOXER TOBOXERBOXER/ TOBOXER solve TOBOXER:length TOBOXERversions TOBOXERapparentlyMACROSdueMACROSduetest TOBOXER: TO BOXERBOXER was error error TOBOXERan TOBOXER SUBMITTER TOBOXERan CODESconfirms error TOBOXERan CODESconfirms TOBOXER/ BOXER new TOBOXERBOXER fieldNONE CODES confirms TO: error error TO errorhisCODESconfirms Customer errorhisCODESconfirmserror seemsduethatduesolves structureduethedueSRLS seemsduethatdueoperatingerrorfieldRTNerrorerror uninitialized of error error error TO used error was used Customer error error CODES confirmserror errorhis CODESof was dueCustomer error error TO CIRCUMVENTION systemtoto / Customer error error error TO errorhis errorhis error error TO error error error TO TO TO error RTNerrorLater was error was test. Customer confirms that the new version of BOXER solves his problem. . The error was apparently due to an uninitialized structure length field that was not used in versions of the operating system. Later version of application code seems to solve the problem. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: his MACROS his solve MACROS his uninitialized his length TO code application not versions application structure test operating BOXER in MODULES BOXER BOXER solves BOXER new was version application TO his Later RTN The his of length in operating problem his CIRCUMVENTION used CIRCUMVENTION CIRCUMVENTION CIRCUMVENTION Later his an uninitialized CIRCUMVENTION Later that errorerrorerrorerrorerrorerror : errorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE MODULES error error errorerrorerrorerrorerrorerror version application errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror NONE: errorerrorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE errorerrorerrorerrorerrorerrorerrorerror problem: errorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerror not: errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE application errorerror errorerrorBOXER. errorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONEapparently errorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE TO TO TO TO TO TO TO fieldNONE TOBOXERBOXER CODESerrorinconfirms TOBOXERBOXER Customer code TOBOXER. duesolve usedTOBOXERBOXER TOBOXERBOXER/ TOBOXER solve TOBOXER:length TOBOXERversions TOBOXERapparentlyMACROSdueMACROSduetest TOBOXER: TO BOXERBOXER was error error TOBOXERan TOBOXER SUBMITTER TOBOXERan CODESconfirms error TOBOXERan CODESconfirms TOBOXER/ BOXER new TOBOXERBOXER fieldNONE CODES confirms TO: error error TO errorhisCODESconfirms Customer errorhisCODESconfirmserror seemsduethatduesolves structureduethedueSRLS seemsduethatdueoperatingerrorfieldRTNerrorerror uninitialized of error error error TO used error was used Customer error error CODES confirmserror errorhis CODESof was dueCustomer error error TO CIRCUMVENTION systemtoto / Customer error error error TO errorhis errorhis error error TO error error error TO TO TO error RTNerrorLater was error was test. Customer confirms that the new version of BOXER solves his problem. . The error was apparently due to an uninitialized structure length field that was not used in versions of the operating system. Later version of application code seems to solve the problem. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: his MACROS his solve MACROS his uninitialized his length TO code application not versions application structure test operating BOXER in MODULES BOXER BOXER solves BOXER new was version application TO his Later RTN The his of length in operating problem his CIRCUMVENTION used CIRCUMVENTION CIRCUMVENTION CIRCUMVENTION Later his an uninitialized CIRCUMVENTION Later that errorerrorerrorerrorerrorerror : errorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE MODULES error error errorerrorerrorerrorerrorerror version application errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror NONE: errorerrorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE errorerrorerrorerrorerrorerrorerrorerror problem: errorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerror not: errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE application errorerror errorerrorBOXER. errorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONEapparently errorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE TO TO TO TO TO TO TO fieldNONE TOBOXERBOXER CODESerrorinconfirms TOBOXERBOXER Customer code TOBOXER. duesolve usedTOBOXERBOXER TOBOXERBOXER/ TOBOXER solve TOBOXER:length TOBOXERversions TOBOXERapparentlyMACROSdueMACROSduetest TOBOXER: TO BOXERBOXER was error error TOBOXERan TOBOXER SUBMITTER TOBOXERan CODESconfirms error TOBOXERan CODESconfirms TOBOXER/ BOXER new TOBOXERBOXER fieldNONE CODES confirms TO: error error TO errorhisCODESconfirms Customer errorhisCODESconfirmserror seemsduethatduesolves structureduethedueSRLS seemsduethatdueoperatingerrorfieldRTNerrorerror uninitialized of error error error TO used error was used Customer error error CODES confirmserror errorhis CODESof was dueCustomer error error TO CIRCUMVENTION systemtoto / Customer error error error TO errorhis errorhis error error TO error error error TO TO TO error RTNerrorLater was error was test. Customer confirms that the new version of BOXER solves his problem. . The error was apparently due to an uninitialized structure length field that was not used in versions of the operating system. Later version of application code seems to solve the problem. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: his MACROS his solve MACROS his uninitialized his length TO code application not versions application structure test operating BOXER in MODULES BOXER BOXER solves BOXER new was version application TO his Later RTN The his of length in operating problem his CIRCUMVENTION used CIRCUMVENTION CIRCUMVENTION CIRCUMVENTION Later his an uninitialized CIRCUMVENTION Later that errorerrorerrorerrorerrorerror : errorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE MODULES error error errorerrorerrorerrorerrorerror version application errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror NONE: errorerrorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE errorerrorerrorerrorerrorerrorerrorerror problem: errorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerror not: errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE application errorerror errorerrorBOXER. errorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONEapparently errorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE TO TO TO TO TO TO TO fieldNONE TOBOXERBOXER CODESerrorinconfirms TOBOXERBOXER Customer code TOBOXER. duesolve usedTOBOXERBOXER TOBOXERBOXER/ TOBOXER solve TOBOXER:length TOBOXERversions TOBOXERapparentlyMACROSdueMACROSduetest TOBOXER: TO BOXERBOXER was error error TOBOXERan TOBOXER SUBMITTER TOBOXERan CODESconfirms error TOBOXERan CODESconfirms TOBOXER/ BOXER new TOBOXERBOXER fieldNONE CODES confirms TO: error error TO errorhisCODESconfirms Customer errorhisCODESconfirmserror seemsduethatduesolves structureduethedueSRLS seemsduethatdueoperatingerrorfieldRTNerrorerror uninitialized of error error error TO used error was used Customer error error CODES confirmserror errorhis CODESof was dueCustomer error error TO CIRCUMVENTION systemtoto / Customer error error error TO errorhis errorhis error error TO error error error TO ═══ 1.4.0.0.1. K CORRUPTION IN DOS AND OS2 FULL SCREEN.C ═══ TO TO error RTN error Later was error was test . Customer confirms that the new version of BOXER solves his problem . . The error was apparently due to an uninitialized structure length field that was not used in versions of the operating system . Later version of application code seems to solve the problem . MODULES / MACROS : SRLS : NONE RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : his MACROS his solve MACROS his uninitialized his length TO code application not versions application structure test operating BOXER in MODULES BOXER BOXER solves BOXER new was version application TO his Later RTN The his of length in operating problem his CIRCUMVENTION used CIRCUMVENTION CIRCUMVENTION CIRCUMVENTION Later his an uninitialized CIRCUMVENTION Later that errorerrorerrorerrorerrorerror : errorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE MODULES error error errorerrorerrorerrorerrorerror version application errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror NONE: errorerrorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE errorerrorerrorerrorerrorerrorerrorerror problem: errorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerror not: errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE application errorerror errorerrorBOXER. errorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONEapparently errorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE TO TO TO TO TO TO TO fieldNONE TOBOXERBOXER CODESerrorinconfirms TOBOXERBOXER Customer code TOBOXER. duesolve usedTOBOXERBOXER TOBOXERBOXER/ TOBOXER solve TOBOXER:length TOBOXERversions TOBOXERapparentlyMACROSdueMACROSduetest TOBOXER: TO BOXERBOXER was error error TOBOXERan TOBOXER SUBMITTER TOBOXERan CODESconfirms error TOBOXERan CODESconfirms TOBOXER/ BOXER new TOBOXERBOXER fieldNONE CODES confirms TO: error error TO errorhisCODESconfirms Customer errorhisCODESconfirmserror seemsduethatduesolves structureduethedueSRLS seemsduethatdueoperatingerrorfieldRTNerrorerror uninitialized of error error error TO used error was used Customer error error CODES confirmserror errorhis CODESof was dueCustomer error error TO CIRCUMVENTION systemtoto / Customer error error error TO errorhis errorhis error error TO error error error TO TO TO error RTNerrorLater was error was test. Customer confirms that the new version of BOXER solves his problem. . The error was apparently due to an uninitialized structure length field that was not used in versions of the operating system. Later version of application code seems to solve the problem. MODULES/MACROS: SRLS: NONE RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: his MACROS his solve MACROS his uninitialized his length TO code application not versions application structure test operating BOXER in MODULES BOXER BOXER solves BOXER new was version application TO his Later RTN The his of length in operating problem his CIRCUMVENTION used CIRCUMVENTION CIRCUMVENTION CIRCUMVENTION Later his an uninitialized CIRCUMVENTION Later that errorerrorerrorerrorerrorerror : errorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE MODULES error error errorerrorerrorerrorerrorerror version application errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror NONE: errorerrorerrorerrorerrorerrorerrorerrorerror ThefieldMACROSfieldMESSAGE errorerrorerrorerrorerrorerrorerrorerror problem: errorerrorerrorerrorerrorerrorerrorerrorerror errorerrorerrorerrorerrorerrorerrorerrorerror not: errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONE application errorerror errorerrorBOXER. errorerror errorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerrorerror fieldNONEapparently errorerrorerrorerrorerrorerror APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen to the os2 fullscreen does not corrupt the video, only from the NOTE:this customer was beta tester,under beta,he was ok. KEYWORDS:WARP XR03000 GD-CL5426 800X600X64K FULL SCREEN CORRUPTION. LOCAL FIX: stay with 256 color. PROBLEM SUMMARY: Customer reported problems wit font/color corruption when using SVGA (800x600x65000) when switching between desktop to full OS2 screen. PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: The problem was looked at and found not to be reproducible. In addition, it was also tested with 256 colors and 65000 colors. The results were shown to John Wobble on 11-07-94. MODULES/MACROS: NONE SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen ═══ 1.4.0.0.1.0.0.0.0.0.0.0.1. 36 - GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR.z ═══ APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen ═══ U FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEADН! ═══ APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Level ////// RECREATION looks corrupted //////// AB01mg02 system back 256 list COMMENTS/for will XR03000/ Symptom ////// AND when SUMMARY /////////// Customer V3 Software /////////////////// 300 Duplicate Date ///////// AB01mg02 DESKTOP /loads /////// 65000 Fullscreen PJ16022 ///////// service screen ///////// 486slc2 Hardware screen //////////// DESKTOP only PROBLEM0300 will VIDEOAPAR stay using // DOS tested Duplicate //& UR1 PJ16022 SCREEN //Parent be Size /////////////////// PROBLEM0300 Release //////SVGA APAR Identifier ...... PJ16022 Last Changed ........ 94/11/11 XR03000 800X600X64K CORRUPTION IN DOS AND OS2 FULL SCREEN. Symptom ...... AB VIDEOAPAR Status ........... CLOSED UR1 Severity ................... 3 Date Closed ......... 94/11/11 Component .......... 562260100 Duplicate of ......... Reported Release ......... 300 Fixed Release ............ 999 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: Release 300 : No PTF planned Parent APAR: Child APAR list: ERROR DESCRIPTION: HARDWARE:****** General Hardware/Software Configuration ****** OS/2 Version: Warp (V3.00) Service Level: Base, No service appl System Brand & Model: Opal IBM SLC2-66 System is a: DESKTOP SYSTEM Processor: 486slc2 System Processor Speed: 66 Mhz System Memory Size: 10 Meg System BIOS Manufacturer: AMI System BIOS Date: 11-11-92 The system boot is: BOOT Manager Clone video card with cirrus 5426 chipset & 1mg vram. SOFTWARE:os2 v3.0(warp).xr03000 cirrus logic svga accelerator driver for 64k color anly.(ex:800x600x64k) 800x600x256 is ok. PROBLEM RECREATION: Customer installed 800x600x65000 and everything looks fine. When he switches from the desktop to an os2 fullscreen session, the video gets corrupted. Switching back to the desktop, the video stays corrupted. It will remain corrupted until he loads a DOS Fullscreen, whch corrects the problem. Switching from the dos fullscreen APAR Identifier ...... PJ16036 Last Changed ........ 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ═══ ! ═══ . . . . . . 94 / 11 / 14 GREAT PLAINS DYNAMICS ( ACCOUNTING ) GET WIN32S ERROR . Symptom . . . . . . AB WINAPAPAR Status . . . . . . . . . . . OPEN 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 : Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM _ BAD _ Handle error . Then press ok 4 times and the following message is displayed : " Win32s Error Dynamics . exe Unhandled Exception detected ( Code : 0x0000005 ) Application will be terminated . " I have installed the win32s support for windows . This has been recreated on mod95 486 / 25dx with the app on LS3 . 0 since the ap requires close to 100 meg free to install . ( Cust is on novell ) LOCAL FIX : none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed ...... 94/11/14 GREAT PLAINS DYNAMICS (ACCOUNTING) GET WIN32S ERROR. Symptom ...... AB WINAPAPAR Status ........... OPEN 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: Trying to launch Great Plains Dynamics from Full Screen Program Manager will cause MEM_BAD_Handle error. Then press ok 4 times and the following message is displayed: "Win32s Error Dynamics.exe Unhandled Exception detected (Code: 0x0000005) Application will be terminated." I have installed the win32s support for windows. This has been recreated on mod95 486/25dx with the app on LS3.0 since the ap requires close to 100 meg free to install. (Cust is on novell) LOCAL FIX: none exe WARP since displayed ap Target / Date Symptom DYNAMICS WARP 222222 with meg 22222222 Component25dx56226010025dx94 ERROR : will launch2Release 2 222222 detected ) 22222222222 none 2222222222222222222 ACCOUNTING PJ16036 Not 222222222 Component25dx56226010025dx94 ok 2win32s 2222222 Application Screen 222222222 222222222 and Symptom 222222222222 ok 25dxACCOUNTING ) 22 Parent PJ16036 22. 22 exe 2222222222222222222 25dxACCOUNTING( 222222 DYNAMICS the 141414141414 V3 GET 1414141414141414 Child24862486 be MEM Then Parent detected requires 14 141414141414 Component ( 1414141414141414141414 Identifier 14141414141414141414141414141414141414 AB Not install 141414141414141414 Child24862486 list 14141414141414141414 APAR PJ16036 141414141414141414 141414141414141414 ACCOUNTING PTF 141414141414141414141414 close list 294 ( 1414 mod95 Not 1414) 1414 error 14141414141414141414141414141414141414 294" 141414141414141414141414 294 onClosed error WIN32SClosed WIN32SClosed ACCOUNTING Closed DYNAMICSClosed GREAT DYNAMICS willClosed PLAINS novellClosed supportClosed0x00000050x00000050x00000050x00000050x00000050x0000005 Special Symptom2 LOCAL 0x00000050x00000050x00000050x00000050x00000050x0000005 (294 Closed)) /1430 ( WARPClosed)) Exception100 Dynamics ( from . Closed) terminated 11Available ( to CodeClosed)) ok (Closed)) and ( Closed) Available ( Closed) 4 following Closed)DESCRIPTION following NotClosed)"4861148611Changed for toClosed) free I Full has ap Great . 562260100 14 Closed 1425dx/014 has WINAPAPAR Current PE Release app is Duplicate14/PlatformClosedbeen0 (BAD to 14 Closed none times cause displayed Plains with press14 Target Reported of Detail Severity 100 Status meg14 ERROR of100 meg14 Type meg Target win32s Code Parent Screen100 LS3 14 Reported OS Severity APAR Identifier ...... PJ16036 Last Changed APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) ═══ CHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTEDx" ═══ APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16039 Last Changed ........ 94/11/04 SHIFT+F10 FAILS TO DISPLAY OBJECT'S CONTEXT MENU FROM LAUNCHPAD DISPLAYING LAUNCHPAD'S CONTEXT MENU INSTEAD Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user right mouse button clicks on an object in a LaunchPad, a context menu for that object will popup. The normal equivalent hot key of Shift+F10 fails to display the object's context menu and instead displays the LaunchPad's context menu. This is incorrect behavior that is inconsistent with the system-wide norm. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD CONTEXT POPUP POP UP MENU SHIFT+F10 SHIFT F10 SHIFT-F10 . LOCAL FIX: . Use a right mouse button click instead of the keystroke combination. . Warp Date Warp Date APAR Date FAILS Date is FAILS WARP Date POPUP OS2WARP Date Target Date - - - - - - Symptom that 11 Name - - - - - - ' 11 a Date ( ( + 04 3 , ' V3 Date ( ( FROM . fails ' incorrect ) Date ( the / click ' Types DESCRIPTION Date ( ( PAD ' Date ( ( Available ' Date ( click ' Date ( 562260100 IN Date ( displays IN OS Date ( 94 / 94 / context in Types Date ( inconsistent XR03000 LAUNCH INSTEAD KEYWORDS behavior key ) : 04 Date 04 2 + , 04 KEYWORDS with DISPLAY POP s Changed List F10 04 + R300 Date combination , ' clicks Types 04 Date OPEN Type Component ERROR PTF WPSHL Release 04 The SCP OS2WPSHL Duplicate Special . system Not 04 for OS2WPSHL . Not 04 UP Not The wide DESCRIPTION Platform Shift . norm 04 SCP PJ16039 Special button LaunchPad )))))) popup LOCAL context 300 )))))) a+/+04 is POPUP FAILS 'APAR( instead Warp for) that )))))) and with system ))))))))))) PE Special ))))))))))))))))))) 3 DISPLAYING Date ))))))))) Detail )))))))))) : F10 OS2WPSHL )))))))) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) ═══ PJ16040 - MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTEDx" ═══ APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . up disconnection ' FROM ) Under closed ( WARP question 17 brought ' remain Closed closed ( ( not ' closed ( ( APAR ' closed ( brought Types ' to closed ( : this Fixed the closed ( Date Fixed MOVES closed ( ; 17 ; 17 Child for remain closed ( from THE is green IN Available If ) A 2 closed WILL 2 300 , . 2 IN Symptom context OF OS become LAUNCH Detail 2 , ON closed CANNOT . ' BUT remain V3 2 closed move Relief Changed destination on THAT only 2 PTF OS2WPSHL NOT DESCRIPTION WILL PE 11 placeholder mark 2 Duplicate NOT 11 mark 2 s mark PTF Special Closed occur Parent 11 LOCAL 2 OS2WPSHL object PE back keeping )))))) of LaunchPad Child 94 )))))) a,17,2 Identifier off DISCONNECTED 'and( GREEN shut Duplicate) problem )))))) an Symptom placeholder ))))))))))) OBJECT PE ))))))))))))))))))) 562260100 Current closed ))))))))) Component )))))))))) A Detail NOT ))))))))UNUSABLE OS2WPSHL OS ))))))))) 94 FIX OS )))))))))))) Component MOVE object,3 Severity selected PJ16040 S )) context PTF Current )) s NOT OS2WARP ))MOVES brought PAD ))))))))))))))))))) object,3 ON )))))))))))) object,3 placeholder DESCRIPTIONALSO MOVES brought OF operation listALSO operation listALSO occur backALSO circle back LEAVESALSO Duplicate DateALSO Reported remain LAUNCHPAD If on disconnection FROM green Parent OPEN manually shadow Changed MARKthatBUTthatif dragging) APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . ═══ 6043 - THE NAME OMNI.OKIDATA XXX IS MISLEADING. THIS DRIVER USES THE EPSON LANGUAGE AND NOT AN OKIDATA LANGUAGE.A# ═══ APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . ═══ THE EPSON LANGUAGE AND NOT AN OKIDATA LANGUAGE.A# ═══ APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . ═══ ING DATAGLANCE V 1.21 ON OS/2 WARPO$ ═══ APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16040 Last Changed ........ 94/11/17 MOVE OF OBJECT FROM LAUNCHPAD VIA OBJECT'S CONTEXT MENU LEAVES A UNUSABLE OBJECT ON THE PAD THAT WILL ALSO BECOME DISCONNECTED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) if a user MOVES an object from the LaunchPad via that object's context menu the object will move to the selected destination BUT an unusable object will remain in the LaunchPad and if the pad is closed and brought back up, either manually or by shut down, the object's placeholder will become a question mark in a green circle, designating the disconnection of the shadow, keeping that object entry on the pad unusable. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL 562260100 R300 WARP OS2WARP LAUNCHPAD LAUNCH PAD MOVE CONTEXT MENU QUESTION MARK GREEN CIRCLE DISCONNECTED CANNOT USE NOT USABLE UNUSABLE . LOCAL FIX: . If the move is performed by dragging the object off the LaunchPad the problem will not occur; this problem will only occur if the object's context menu is used for the move operation. . APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief ═══ HEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2R% ═══ APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: Relief esi defect LOCAL 18 Available Relief Fixed has Relief Duplicate Relief Not up fff7a17f frames 00006432 Reported Not up Identifier frames DATAGLANCE Relief Fixed OTHERAPAR : ERROR defect Symptom cmp Relief esi installation ) ) ss 0170 cs )))))) na DOSHIGH32CODE 21 )))))))) 00000000+,+- es fs FIX cr2 E Trap FIX Page = eip eax 00006446 ss FIX HL Release list ptr Types 001e2000 11 already program )))))) DataGlance vmDecommitMemWrkr Present ))))))))))) info PE ))))))))))))))))))) / a 6d ))))))))) 94 )))))))))) 0000 been gs ))))))))) os2krnl ON ))))))))) 00 Closed ON )))))))))))) 94 Fault iopl+. trap to Platform SCP )) A PTF a )) RUNNING gs OPEN ))fff7a1ec 0EH Parent ))))))))))))))))))) iopl+. nc )))))))))))) iopl+. Present After0000359f fff7a1ec 0EH LN nv ebx0000359f nv ebx0000359f List 01700000359f 300 0170 ebp0000359f Changed ab7c2e960000359f ) Severity iopl+. Type the WARP# DATAGLANCE 00017a20 Target esp 0030 Fixed Component Relief Duplicate TRAP Read Fixed OTHERAPAR : ERROR Relief Fixed up esi rf Relief pe Access 17a10000 0030 Special Fixed up OS Date Relief Duplicate 0168 DATAGLANCE Relief ldrSetVMflags defect 66833800 0168 14 1 start( capture edi invalid 18 pl attempting( Relief Fixed OTHERAPAR Name up 103120 00017a20 nz edx Date 00017a20 cr3 562260100( ab7c2efe Relief APAR gs Relief PJ16049( DESCRIPTION Read Fixed causes Here Relief APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: ═══ 1.4.0.0.1.0.0.0.0.0.0.0.1.1. 86SLC2R% ═══ APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16049 Last Changed ........ 94/11/18 TRAP E WHEN RUNNING DATAGLANCE V 1.21 ON OS/2 WARP Symptom ...... HL OTHERAPAR Status ........... OPEN Severity ................... 2 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: After installation of DataGlance 1.21 on WARP, attempting to start the capture frames program causes a TRAP E. Here is the trap info: . Trap 14 (0EH) - Page Fault 0000, Not Present, Read Access, Supervisor eax=00000000 ebx=ab7c2efe ecx=0000359f edx=17a10000 esi=ab7c2e96 edi=00017a20 eip=fff7a17f esp=00006432 ebp=00006446 iopl=2 rf -- -- nv up ei pl nz na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=00000000 cr3=001e2000 0170:fff7a17f 66833800 cmp word ptr eax ,+00 ds:00000000=invalid ##LN 0170:fff7a128 os2krnl:DOSHIGH32CODE:_vmDecommitMemWrkr + 57 0170:fff7a1ec _ldrSetVMflags - 6d . A defect has already been created (103120). LOCAL FIX: APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A ═══ 1.4.0.1. 16053 - SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2R% ═══ ═══ PJ16064 - 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8)c' ═══ 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A 00000000 00000000 00000000 00000000 00000000 00000000 240mb Changed GSACC 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 no N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 23 Duplicate N 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 AMBRA following Identifier 00000030 150b PTF printers " ON Platform 00000000 00000000 at P3 bed80000 00000000 00000000 ( PJ16053 GSACC Name 00000000 00000000 FSACC = OK 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b list 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Identifier 00000030 150b OS2 C 4 FSACC = Internal listing ffffffff 4 listing ffffffff 4 INSTALLING 94 4 after 94 External 4 Current By 4 80486SLC2 ES GSACC AWARD 001f03af 00000000 2 GSLIM PTF / : Paradise OS P4 a EAX listed AB 5 PE Child 00000000 EDI ESLIM P4 PID ERROR 4 00000000 Parent 00fb * 001f , 0000 Installing desktop 0000a8cc / FSACC List / maintenance 66mhz / P1 choosing 486SLC2 0000a92d Closed 486SLC2 562260100 Component 486SLC2 0000bee8 CS 486SLC2 1 Default 486SLC2 50 Configuration 486SLC2 0003 CSLIM 486SLC2 DS DESCRIPTION 486SLC2 0000d12f clone 486SLC2 00012246 ESI 486SLC2 150b Not 0000 0000 0000 0000 FSLIM Printer CSACC Last GS FLG INSTLAPAR FS APAR 486SLC2 0015ef50 OPEN 486SLC2 0005 case 486SLC2 0015a8e8 Date 486SLC2 0015a8e8 EBP 486SLC2 0000a8cc EBX 486SLC2 0000a8cc AN 486SLC2 0000a92d an 486SLC2 000320ea 0015ef50 4 DS 300 Ambra RAM LOCAL choosing / . 000020ea case 4 0000a92d 486SLC2 ESACC ) ) FIX 0015ef50 4 Detail In 4 c0000005 4 Release Processor . 25 0015ef50 4 DSACC Release EXE 0000 33mhz 00000000 4mb bios ECX 8mb A another * 008f , 00000000 Fixed DSLIM 4 ECX ON , , , C 0000bee8 PRINTER printers Processor ESP 0000a8cc GSLIM PID ESLIM Child case External Date 486SLC2 CSLIM GSACC CSACC another 25 8mb 150b P1 Detail OS2 OPEN , Component after 0000bee8 , at Name Default bios Fixed 11 = Name Duplicate ECX Name Changed Name FSACC Printer DS EAX 0000d12f no FSACC Printer EIP EAX Available Name Duplicate " INSTALL 4 Current bios P2 Ambra Name Default ES , , EIP DS 0000bee8 ide 0015ef50 GSACC also CSLIM case 66mhz 000320ea List : 94 ) AB INSTALLING a 562260100 " 33mhz 000320ea . ( 00f3 is 11 GS ) bios bed80000 c0000005 GSACC list FS Ambra listing ) harddisk AWARD 150b ESACC DSACC Current 0000d12f * 000020ea LOCAL GSACC 008f DSACC Component ) , Fixed GSACC 001f EXE 25 Identifier / CS APAR Identifier ...... PJ16053 Last Changed ........ 94/11/23 SYS3175 WHEN INSTALLING OS/2 WARP ON AN AMBRA SLIMLINE 80486SLC2 Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Installing OS/2 WARP on an Ambra Slimline 80486SLC2 result SYS3175 on INSTALL.EXE on the maintenance desktop. By choosing OK after seeing the System Configuration screen, the PRINTER listing will shows no printers listed. After choosing OK at the "Select System Default Printer" screen, will result the following: SYS3175 PID 0005 C:\OS2\INSTALL\INSTALL.EXE c0000005 000320ea P1=00000000 P2=ffffffff P3=XXXXXXXX P4=XXXXXXXX EAX=00000000 EBX=00000000 ECX=0000bee8 EDX=bed80000 ESI=0015ef50 EDI=001f03af DS=008f DSACC=00f3 DSLIM=0000d12f ES=0000 ESACC=**** ESLIM=******** FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=001f:000020ea CSACC=00fb CSLIM=0000a92d SS:ESP=008f:0000a8cc SSACC=00f3 SSLIM=0000d12f EBP=0015a8e8 FLG=00012246 INSTALL.EXE 0003:000020ea ... System is an Ambra Slimline SLC2 25/33mhz (External) 50/66mhz (Internal) Processor, 4mb RAM (8mb also), 240mb harddisk. . In another case, on a clone with 486SLC2 66mhz, 4mb ram, an AWARD 4.5 bios, Paradise VGA, ide 340mb harddisk. LOCAL FIX: N/A APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd number of bytes is being returned. The Sony drives are initializing in improper mode. LOCAL FIX: None currently. inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in inquiry Warp 222222 mode 22222222 ERROR23CDROM23Closed 23Child IN improper drives 222222 fully 22222222222 2222222222222222222 cdrom OS not 222222222 Not 2222222222 drive Release 222222222 222222222 Component that 222222222222 Not 23Child 22 OPEN OS 22' 22 L1OK 2222222222222222222 23Child 222222222222 23Child PJ16058even L1OK even even inquiryeven Name inquiry even Severity Parenteven WORK 23Child in Identifier drives work2support PE2 LOCAL None IBM1S506 number 11 2 FX001DE None is , OS2 , 11 theeven APAR MCevenworkwork2support MITSUMI and FIX55D FIXSymptom FIX FIX ReliefFIX55D returnFIX55D returnedFIXADD SFIXlist SonyFIXATAPI sFIXbeing PlatformFIXbut providesFIXbytes PTFFIXAn shouldFIX300 SONYFIX1111 SpecialFIX11111111 TheseFIXChanged theseFIXbytes threeFIX55E toFIX300 Type111 TypesFIX11111111 oddevenSCPFIXAvailableeven562260100 ofFIXcase onFIX: evenStatusFIXbuteven94 FIXbytes FIXAn ReportedFIXare TheFIXan work2support ANDeven562260100 222 in Identifier compliant23Current .supported/ DO23driver ./ 11 Detail .Duplicate IDE/11 command V32 2 will initializing Mitsumi11 for NOT DESCRIPTION driver11 Detail 11 in Last Date2DISKAPAR List11 11 WARP currently V32 Targeteven 23Fixed APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: ═══ DO NOT WORK IN WARP. L1OKe& ═══ REOP Fixed : Target Fixed 486 v3 / SUBMITTER 562260100 FIX 2 / / / WILL install Identifier come 0 Component ( SUMMARY ) DESCRIPTION 0 drivers ( Warp ) . Current ( Duplicate Hardware ) . CODES ULTRA / / using INSTALL MACROS . GRAPHICS MODULES corrupt drivers . Current . install List continue / Date Mach32 . . Ultra CONCLUSION ULTRA / system FIX 0 get 94 94 Identifier (((((( PROBLEM List CIRCUMVENTION (((((((( 28800).)0 SOFTWARE 18 562260100 11 Mach8 HARDWARE Child select DESCRIPTION MODULES V3 Install Ultra( list Symptom (((((( MACH8 Date Status ((((((((((( OS Selective ((((((((((((((((((( - continue Closed ((((((((( COMMENTS (((((((((( 2 Duplicate of ((((((((( REOP Release ((((((((( 1 get Release (((((((((((( COMMENTS menu Parent)/ Ultra ULTRA SRLS Types (( Component system continue (( Type of Relief ((NOT After Select ((((((((((((((((((( Parent)/ PTF (((((((((((( Parent)/ Status Current3 NOT After Platform RECREATION Mach323 RECREATION Mach323 PJ16064 943 clone 94 LOCAL3 ERROR corrupt3 Target Special 18 Special 11 8514 MACROS HARDWARE Changed SCP using Name v3 install up( THE : Hardware Changed SCP SYSTEMS : ON TEMPORARY SUMMARY LOCAL GRAPHICS PE up( Target up hardware(300 drivers recognized A SUBMITTER GRAPHICS Hardware Changed SCP APAR the through Changed SCP : Name Graphics A come( ( 386 KEYWORDS CODES TO 486 APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: REOP Fixed : Target Fixed 486 v3 / SUBMITTER 562260100 FIX 2 / / / WILL install Identifier come 0 Component ( SUMMARY ) DESCRIPTION 0 drivers ( Warp ) . Current ( Duplicate Hardware ) . CODES ULTRA / / using INSTALL MACROS . GRAPHICS MODULES corrupt drivers . Current . install List continue / Date Mach32 . . Ultra CONCLUSION ULTRA / system FIX 0 get 94 94 Identifier (((((( PROBLEM List CIRCUMVENTION (((((((( 28800).)0 SOFTWARE 18 562260100 11 Mach8 HARDWARE Child select DESCRIPTION MODULES V3 Install Ultra( list Symptom (((((( MACH8 Date Status ((((((((((( OS Selective ((((((((((((((((((( - continue Closed ((((((((( COMMENTS (((((((((( 2 Duplicate of ((((((((( REOP Release ((((((((( 1 get Release (((((((((((( COMMENTS menu Parent)/ Ultra ULTRA SRLS Types (( Component system continue (( Type of Relief ((NOT After Select ((((((((((((((((((( Parent)/ PTF (((((((((((( Parent)/ Status Current3 NOT After Platform RECREATION Mach323 RECREATION Mach323 PJ16064 943 clone 94 LOCAL3 ERROR corrupt3 Target Special 18 Special 11 8514 MACROS HARDWARE Changed SCP using Name v3 install up( THE : Hardware Changed SCP SYSTEMS : ON TEMPORARY SUMMARY LOCAL GRAPHICS PE up( Target up hardware(300 drivers recognized A SUBMITTER GRAPHICS Hardware Changed SCP APAR the through Changed SCP : Name Graphics A come( ( 386 KEYWORDS CODES TO 486 APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: REOP Fixed : Target Fixed 486 v3 / SUBMITTER 562260100 FIX 2 / / / WILL install Identifier come 0 Component ( SUMMARY ) DESCRIPTION 0 drivers ( Warp ) . Current ( Duplicate Hardware ) . CODES ULTRA / / using INSTALL MACROS . GRAPHICS MODULES corrupt drivers . Current . install List continue / Date Mach32 . . Ultra CONCLUSION ULTRA / system FIX 0 get 94 94 Identifier (((((( PROBLEM List CIRCUMVENTION (((((((( 28800).)0 SOFTWARE 18 562260100 11 Mach8 HARDWARE Child select DESCRIPTION MODULES V3 Install Ultra( list Symptom (((((( MACH8 Date Status ((((((((((( OS Selective ((((((((((((((((((( - continue Closed ((((((((( COMMENTS (((((((((( 2 Duplicate of ((((((((( REOP Release ((((((((( 1 get Release (((((((((((( COMMENTS menu Parent)/ Ultra ULTRA SRLS Types (( Component system continue (( Type of Relief ((NOT After Select ((((((((((((((((((( Parent)/ PTF (((((((((((( Parent)/ Status Current3 NOT After Platform RECREATION Mach323 RECREATION Mach323 PJ16064 943 clone 94 LOCAL3 ERROR corrupt3 Target Special 18 Special 11 8514 MACROS HARDWARE Changed SCP using Name v3 install up( THE : Hardware Changed SCP SYSTEMS : ON TEMPORARY SUMMARY LOCAL GRAPHICS PE up( Target up hardware(300 drivers recognized A SUBMITTER GRAPHICS Hardware Changed SCP APAR the through Changed SCP : Name Graphics A come( ( 386 KEYWORDS CODES TO 486 APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: REOP Fixed : Target Fixed 486 v3 / SUBMITTER 562260100 FIX 2 / / / WILL install Identifier come 0 Component ( SUMMARY ) DESCRIPTION 0 drivers ( Warp ) . Current ( Duplicate Hardware ) . CODES ULTRA / / using INSTALL MACROS . GRAPHICS MODULES corrupt drivers . Current . install List continue / Date Mach32 . . Ultra CONCLUSION ULTRA / system FIX 0 get 94 94 Identifier (((((( PROBLEM List CIRCUMVENTION (((((((( 28800).)0 SOFTWARE 18 562260100 11 Mach8 HARDWARE Child select DESCRIPTION MODULES V3 Install Ultra( list Symptom (((((( MACH8 Date Status ((((((((((( OS Selective ((((((((((((((((((( - continue Closed ((((((((( COMMENTS (((((((((( 2 Duplicate of ((((((((( REOP Release ((((((((( 1 get Release (((((((((((( COMMENTS menu Parent)/ Ultra ULTRA SRLS Types (( Component system continue (( Type of Relief ((NOT After Select ((((((((((((((((((( Parent)/ PTF (((((((((((( Parent)/ Status Current3 NOT After Platform RECREATION Mach323 RECREATION Mach323 PJ16064 943 clone 94 LOCAL3 ERROR corrupt3 Target Special 18 Special 11 8514 MACROS HARDWARE Changed SCP using Name v3 install up( THE : Hardware Changed SCP SYSTEMS : ON TEMPORARY SUMMARY LOCAL GRAPHICS PE up( Target up hardware(300 drivers recognized A SUBMITTER GRAPHICS Hardware Changed SCP APAR the through Changed SCP : Name Graphics A come( ( 386 KEYWORDS CODES TO 486 APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: REOP Fixed : Target Fixed 486 v3 / SUBMITTER 562260100 FIX 2 / / / WILL install Identifier come 0 Component ( SUMMARY ) DESCRIPTION 0 drivers ( Warp ) . Current ( Duplicate Hardware ) . CODES ULTRA / / using INSTALL MACROS . GRAPHICS MODULES corrupt drivers . Current . install List continue / Date Mach32 . . Ultra CONCLUSION ULTRA / system FIX 0 get 94 94 Identifier (((((( PROBLEM List CIRCUMVENTION (((((((( 28800).)0 SOFTWARE 18 562260100 11 Mach8 HARDWARE Child select DESCRIPTION MODULES V3 Install Ultra( list Symptom (((((( MACH8 Date Status ((((((((((( OS Selective ((((((((((((((((((( - continue Closed ((((((((( COMMENTS (((((((((( 2 Duplicate of ((((((((( REOP Release ((((((((( 1 get Release (((((((((((( COMMENTS menu Parent)/ Ultra ULTRA SRLS Types (( Component system continue (( Type of Relief ((NOT After Select ((((((((((((((((((( Parent)/ PTF (((((((((((( Parent)/ Status Current3 NOT After Platform RECREATION Mach323 RECREATION Mach323 PJ16064 943 clone 94 LOCAL3 ERROR corrupt3 Target Special 18 Special 11 8514 MACROS HARDWARE Changed SCP using Name v3 install up( THE : Hardware Changed SCP SYSTEMS : ON TEMPORARY SUMMARY LOCAL GRAPHICS PE up( Target up hardware(300 drivers recognized A SUBMITTER GRAPHICS Hardware Changed SCP APAR the through Changed SCP : Name Graphics A come( ( 386 KEYWORDS CODES TO 486 APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: REOP Fixed : Target Fixed 486 v3 / SUBMITTER 562260100 FIX 2 / / / WILL install Identifier come 0 Component ( SUMMARY ) DESCRIPTION 0 drivers ( Warp ) . Current ( Duplicate Hardware ) . CODES ULTRA / / using INSTALL MACROS . GRAPHICS MODULES corrupt drivers . Current . install List continue / Date Mach32 . . Ultra CONCLUSION ULTRA / system FIX 0 get 94 94 Identifier (((((( PROBLEM List CIRCUMVENTION (((((((( 28800).)0 SOFTWARE 18 562260100 11 Mach8 HARDWARE Child select DESCRIPTION MODULES V3 Install Ultra( list Symptom (((((( MACH8 Date Status ((((((((((( OS Selective ((((((((((((((((((( - continue Closed ((((((((( COMMENTS (((((((((( 2 Duplicate of ((((((((( REOP Release ((((((((( 1 get Release (((((((((((( COMMENTS menu Parent)/ Ultra ULTRA SRLS Types (( Component system continue (( Type of Relief ((NOT After Select ((((((((((((((((((( Parent)/ PTF (((((((((((( Parent)/ Status Current3 NOT After Platform RECREATION Mach323 RECREATION Mach323 PJ16064 943 clone 94 LOCAL3 ERROR corrupt3 Target Special 18 Special 11 8514 MACROS HARDWARE Changed SCP using Name v3 install up( THE : Hardware Changed SCP SYSTEMS : ON TEMPORARY SUMMARY LOCAL GRAPHICS PE up( Target up hardware(300 drivers recognized A SUBMITTER GRAPHICS Hardware Changed SCP APAR the through Changed SCP : Name Graphics A come( ( 386 KEYWORDS CODES TO 486 APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: REOP Fixed : Target Fixed 486 v3 / SUBMITTER 562260100 FIX 2 / / / WILL install Identifier come 0 Component ( SUMMARY ) DESCRIPTION 0 drivers ( Warp ) . Current ( Duplicate Hardware ) . CODES ULTRA / / using INSTALL MACROS . GRAPHICS MODULES corrupt drivers . Current . install List continue / Date Mach32 . . Ultra CONCLUSION ULTRA / system FIX 0 get 94 94 Identifier (((((( PROBLEM List CIRCUMVENTION (((((((( 28800).)0 SOFTWARE 18 562260100 11 Mach8 HARDWARE Child select DESCRIPTION MODULES V3 Install Ultra( list Symptom (((((( MACH8 Date Status ((((((((((( OS Selective ((((((((((((((((((( - continue Closed ((((((((( COMMENTS (((((((((( 2 Duplicate of ((((((((( REOP Release ((((((((( 1 get Release (((((((((((( COMMENTS menu Parent)/ Ultra ULTRA SRLS Types (( Component system continue (( Type of Relief ((NOT After Select ((((((((((((((((((( Parent)/ PTF (((((((((((( Parent)/ Status Current3 NOT After Platform RECREATION Mach323 RECREATION Mach323 PJ16064 943 clone 94 LOCAL3 ERROR corrupt3 Target Special 18 Special 11 8514 MACROS HARDWARE Changed SCP using Name v3 install up( THE : Hardware Changed SCP SYSTEMS : ON TEMPORARY SUMMARY LOCAL GRAPHICS PE up( Target up hardware(300 drivers recognized A SUBMITTER GRAPHICS Hardware Changed SCP APAR the through Changed SCP : Name Graphics A come( ( 386 KEYWORDS CODES TO 486 APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: REOP Fixed : Target Fixed 486 v3 / SUBMITTER 562260100 FIX 2 / / / WILL install Identifier come 0 Component ( SUMMARY ) DESCRIPTION 0 drivers ( Warp ) . Current ( Duplicate Hardware ) . CODES ULTRA / / using INSTALL MACROS . GRAPHICS MODULES corrupt drivers . Current . install List continue / Date Mach32 . . Ultra CONCLUSION ULTRA / system FIX 0 get 94 94 Identifier (((((( PROBLEM List CIRCUMVENTION (((((((( 28800).)0 SOFTWARE 18 562260100 11 Mach8 HARDWARE Child select DESCRIPTION MODULES V3 Install Ultra( list Symptom (((((( MACH8 Date Status ((((((((((( OS Selective ((((((((((((((((((( - continue Closed ((((((((( COMMENTS (((((((((( 2 Duplicate of ((((((((( REOP Release ((((((((( 1 get Release (((((((((((( COMMENTS menu Parent)/ Ultra ULTRA SRLS Types (( Component system continue (( Type of Relief ((NOT After Select ((((((((((((((((((( Parent)/ PTF (((((((((((( Parent)/ Status Current3 NOT After Platform RECREATION Mach323 RECREATION Mach323 PJ16064 943 clone 94 LOCAL3 ERROR corrupt3 Target Special 18 Special 11 8514 MACROS HARDWARE Changed SCP using Name v3 install up( THE : Hardware Changed SCP SYSTEMS : ON TEMPORARY SUMMARY LOCAL GRAPHICS PE up( Target up hardware(300 drivers recognized A SUBMITTER GRAPHICS Hardware Changed SCP APAR the through Changed SCP : Name Graphics A come( ( 386 KEYWORDS CODES TO 486 APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: REOP Fixed : Target Fixed 486 v3 / SUBMITTER 562260100 FIX 2 / / / WILL install Identifier come 0 Component ( SUMMARY ) DESCRIPTION 0 drivers ( Warp ) . Current ( Duplicate Hardware ) . CODES ULTRA / / using INSTALL MACROS . GRAPHICS MODULES corrupt drivers . Current . install List continue / Date Mach32 . . Ultra CONCLUSION ULTRA / system FIX 0 get 94 94 Identifier (((((( PROBLEM List CIRCUMVENTION (((((((( 28800).)0 SOFTWARE 18 562260100 11 Mach8 HARDWARE Child select DESCRIPTION MODULES V3 Install Ultra( list Symptom (((((( MACH8 Date Status ((((((((((( OS Selective ((((((((((((((((((( - continue Closed ((((((((( COMMENTS (((((((((( 2 Duplicate of ((((((((( REOP Release ((((((((( 1 get Release (((((((((((( COMMENTS menu Parent)/ Ultra ULTRA SRLS Types (( Component system continue (( Type of Relief ((NOT After Select ((((((((((((((((((( Parent)/ PTF (((((((((((( Parent)/ Status Current3 NOT After Platform RECREATION Mach323 RECREATION Mach323 PJ16064 943 clone 94 LOCAL3 ERROR corrupt3 Target Special 18 Special 11 8514 MACROS HARDWARE Changed SCP using Name v3 install up( THE : Hardware Changed SCP SYSTEMS : ON TEMPORARY SUMMARY LOCAL GRAPHICS PE up( Target up hardware(300 drivers recognized A SUBMITTER GRAPHICS Hardware Changed SCP APAR the through Changed SCP : Name Graphics A come( ( 386 KEYWORDS CODES TO 486 APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: REOP Fixed : Target Fixed 486 v3 / SUBMITTER 562260100 FIX 2 / / / WILL install Identifier come 0 Component ( SUMMARY ) DESCRIPTION 0 drivers ( Warp ) . Current ( Duplicate Hardware ) . CODES ULTRA / / using INSTALL MACROS . GRAPHICS MODULES corrupt drivers . Current . install List continue / Date Mach32 . . Ultra CONCLUSION ULTRA / system FIX 0 get 94 94 Identifier (((((( PROBLEM List CIRCUMVENTION (((((((( 28800).)0 SOFTWARE 18 562260100 11 Mach8 HARDWARE Child select DESCRIPTION MODULES V3 Install Ultra( list Symptom (((((( MACH8 Date Status ((((((((((( OS Selective ((((((((((((((((((( - continue Closed ((((((((( COMMENTS (((((((((( 2 Duplicate of ((((((((( REOP Release ((((((((( 1 get Release (((((((((((( COMMENTS menu Parent)/ Ultra ULTRA SRLS Types (( Component system continue (( Type of Relief ((NOT After Select ((((((((((((((((((( Parent)/ PTF (((((((((((( Parent)/ Status Current3 NOT After Platform RECREATION Mach323 RECREATION Mach323 PJ16064 943 clone 94 LOCAL3 ERROR corrupt3 Target Special 18 Special 11 8514 MACROS HARDWARE Changed SCP using Name v3 install up( THE : Hardware Changed SCP SYSTEMS : ON TEMPORARY SUMMARY LOCAL GRAPHICS PE up( Target up hardware(300 drivers recognized A SUBMITTER GRAPHICS Hardware Changed SCP APAR the through Changed SCP : Name Graphics A come( ( 386 KEYWORDS CODES TO 486 APAR Identifier ...... PJ16064 Last Changed ........ 94/11/18 28800/MACH8 DRIVERS WILL NOT INSTALL ON SYSTEMS WITH THE GRAPHICS ULTRA (WITH A MACH8) Symptom ...... MC VIDEOAPAR Status ........... REOP Severity ................... 2 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: HARDWARE : ATI Graphics Ultra (mach8) 386/486 clone SOFTWARE : OS/2 Warp v3.0 PROBLEM RECREATION : 1. Install OS/2 Warp v3.0 2. Selective install Mach8 drivers - Hardware not recognized 3. Select continue after hardware select menu - After install (if you get through the install) will come up corrupt. KEYWORDS : ATI Mach8 Graphics Ultra Install Selective install LOCAL FIX: 1. Install the system using the 8514 drivers 2. Install the system using the Mach32 drivers PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd number of bytes is being returned. The Sony drives are initializing in improper mode. LOCAL FIX: None currently. but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd ═══ ' ═══ but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd ═══ ERSB( ═══ but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd ═══ 075 - APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION.|* ═══ but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd but Identifier 111111111111 Parent is cdrom 1111111111111111 APAR255D255E 942MC drives Not initializing on that These for V3 . ATAPI MC/ Symptom 111111111111 mode 'Status 1111111111111111111111 Reported should 11111111111111111111111111111111111111 562260100 DISKAPAR Closed 111111111111111111 Current 11111111111111111111 AND Duplicate of 111111111111111111 return Release 111111111111111111 ADD FIX Release 111111111111111111111111 Current not OPEN2562260100 WORK'Sony Types 1111 Detail The DISKAPAR 1111, Type of Relief 1111odd case s 11111111111111111111111111111111111111 OPEN2562260100 PE 111111111111111111111111 OPEN2562260100 Status driveare odd case OS2 Platform Lastare Platform Lastare OS butare CDROM but L1OKare ERROR DOare FX001DE are bytes fully WARP .LOCAL/ ,An2an Child SONY are OPEN2562260100 work1123 PJ16058 PTF are 30011 IN OPEN2562260100 work1123 56226010011 Severity in MITSUMI driver 1 IDE number provides :11 SCP Date being IBM1S506 S Name 1 Available in .improper Fixed three these in/ 'compliant Warp DESCRIPTION11 inquiry are bytes MITSUMI fully WARP IN Severity in list evenare 30011 IN these Target will these and driver 56226010011 IN these Target will these List driver PJ16058 supportedare PJ16058 currentlyare evenare Componentare NOT2Mitsumiare Specialare returned commandare Changedare None to supportare APAR APAR Identifier ...... PJ16058 Last Changed ........ 94/11/23 SONY 55E AND 55D, MITSUMI FX001DE CDROM'S DO NOT WORK IN WARP. L1OK Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 1 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: The Sony 55E, Sony 55D, and Mitsumi FX001DE cdrom's will not work in OS2 Warp. These are IDE cdrom's that are on the supported list for OS2 Warp. The Warp IBM1S506.ADD driver provides ATAPI support for IDE cdrom's, but these three cdrom's are not fully ATAPI compliant. . An inquiry command to an ATAPI compliant cdrom should return an even number of bytes, but in the case of the Mitsumi drive, an odd APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 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: Adaptec 1640 MCA card with a CDROM attached under warp fails to see the cdrom under WARP 3.0. The problem is in the AHA164x.add LOCAL FIX: Use older driver (ie 2.11) CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 )) DISKAPAR Duplicate )) to ))The Available ))))))))))))))))))) UNDER.11 warp )))))))))))) UNDER.11 FAILS94 The Available Use with Relief94 with Relief94 UR AHA164x94 Component AHA164x Release94 is ERROR94 3( 22( add see Name Changed Target Parent under ) APAR of Changed APAR Type Release LOCAL under ) Not): Identifier WARP attached LOCAL of Changed ( CARD Changed APAR Target MCA attached DESCRIPTION) ) a PJ16074 Date Adaptec attached DESCRIPTION Changed Adaptec Last the to cdrom( CARD Parent CDROM to see Fixed( Adaptec TO APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 )) DISKAPAR Duplicate )) to ))The Available ))))))))))))))))))) UNDER.11 warp )))))))))))) UNDER.11 FAILS94 The Available Use with Relief94 with Relief94 UR AHA164x94 Component AHA164x Release94 is ERROR94 3( 22( add see Name Changed Target Parent under ) APAR of Changed APAR Type Release LOCAL under ) Not): Identifier WARP attached LOCAL of Changed ( CARD Changed APAR Target MCA attached DESCRIPTION) ) a PJ16074 Date Adaptec attached DESCRIPTION Changed Adaptec Last the to cdrom( CARD Parent CDROM to see Fixed( Adaptec TO APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 )) DISKAPAR Duplicate )) to ))The Available ))))))))))))))))))) UNDER.11 warp )))))))))))) UNDER.11 FAILS94 The Available Use with Relief94 with Relief94 UR AHA164x94 Component AHA164x Release94 is ERROR94 3( 22( add see Name Changed Target Parent under ) APAR of Changed APAR Type Release LOCAL under ) Not): Identifier WARP attached LOCAL of Changed ( CARD Changed APAR Target MCA attached DESCRIPTION) ) a PJ16074 Date Adaptec attached DESCRIPTION Changed Adaptec Last the to cdrom( CARD Parent CDROM to see Fixed( Adaptec TO APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 )) DISKAPAR Duplicate )) to ))The Available ))))))))))))))))))) UNDER.11 warp )))))))))))) UNDER.11 FAILS94 The Available Use with Relief94 with Relief94 UR AHA164x94 Component AHA164x Release94 is ERROR94 3( 22( add see Name Changed Target Parent under ) APAR of Changed APAR Type Release LOCAL under ) Not): Identifier WARP attached LOCAL of Changed ( CARD Changed APAR Target MCA attached DESCRIPTION) ) a PJ16074 Date Adaptec attached DESCRIPTION Changed Adaptec Last the to cdrom( CARD Parent CDROM to see Fixed( Adaptec TO APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 )) DISKAPAR Duplicate )) to ))The Available ))))))))))))))))))) UNDER.11 warp )))))))))))) UNDER.11 FAILS94 The Available Use with Relief94 with Relief94 UR AHA164x94 Component AHA164x Release94 is ERROR94 3( 22( add see Name Changed Target Parent under ) APAR of Changed APAR Type Release LOCAL under ) Not): Identifier WARP attached LOCAL of Changed ( CARD Changed APAR Target MCA attached DESCRIPTION) ) a PJ16074 Date Adaptec attached DESCRIPTION Changed Adaptec Last the to cdrom( CARD Parent CDROM to see Fixed( Adaptec TO APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 )) DISKAPAR Duplicate )) to ))The Available ))))))))))))))))))) UNDER.11 warp )))))))))))) UNDER.11 FAILS94 The Available Use with Relief94 with Relief94 UR AHA164x94 Component AHA164x Release94 is ERROR94 3( 22( add see Name Changed Target Parent under ) APAR of Changed APAR Type Release LOCAL under ) Not): Identifier WARP attached LOCAL of Changed ( CARD Changed APAR Target MCA attached DESCRIPTION) ) a PJ16074 Date Adaptec attached DESCRIPTION Changed Adaptec Last the to cdrom( CARD Parent CDROM to see Fixed( Adaptec TO APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 )) DISKAPAR Duplicate )) to ))The Available ))))))))))))))))))) UNDER.11 warp )))))))))))) UNDER.11 FAILS94 The Available Use with Relief94 with Relief94 UR AHA164x94 Component AHA164x Release94 is ERROR94 3( 22( add see Name Changed Target Parent under ) APAR of Changed APAR Type Release LOCAL under ) Not): Identifier WARP attached LOCAL of Changed ( CARD Changed APAR Target MCA attached DESCRIPTION) ) a PJ16074 Date Adaptec attached DESCRIPTION Changed Adaptec Last the to cdrom( CARD Parent CDROM to see Fixed( Adaptec TO APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 )) DISKAPAR Duplicate )) to ))The Available ))))))))))))))))))) UNDER.11 warp )))))))))))) UNDER.11 FAILS94 The Available Use with Relief94 with Relief94 UR AHA164x94 Component AHA164x Release94 is ERROR94 3( 22( add see Name Changed Target Parent under ) APAR of Changed APAR Type Release LOCAL under ) Not): Identifier WARP attached LOCAL of Changed ( CARD Changed APAR Target MCA attached DESCRIPTION) ) a PJ16074 Date Adaptec attached DESCRIPTION Changed Adaptec Last the to cdrom( CARD Parent CDROM to see Fixed( Adaptec TO APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 )) DISKAPAR Duplicate )) to ))The Available ))))))))))))))))))) UNDER.11 warp )))))))))))) UNDER.11 FAILS94 The Available Use with Relief94 with Relief94 UR AHA164x94 Component AHA164x Release94 is ERROR94 3( 22( add see Name Changed Target Parent under ) APAR of Changed APAR Type Release LOCAL under ) Not): Identifier WARP attached LOCAL of Changed ( CARD Changed APAR Target MCA attached DESCRIPTION) ) a PJ16074 Date Adaptec attached DESCRIPTION Changed Adaptec Last the to cdrom( CARD Parent CDROM to see Fixed( Adaptec TO APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 )) DISKAPAR Duplicate )) to ))The Available ))))))))))))))))))) UNDER.11 warp )))))))))))) UNDER.11 FAILS94 The Available Use with Relief94 with Relief94 UR AHA164x94 Component AHA164x Release94 is ERROR94 3( 22( add see Name Changed Target Parent under ) APAR of Changed APAR Type Release LOCAL under ) Not): Identifier WARP attached LOCAL of Changed ( CARD Changed APAR Target MCA attached DESCRIPTION) ) a PJ16074 Date Adaptec attached DESCRIPTION Changed Adaptec Last the to cdrom( CARD Parent CDROM to see Fixed( Adaptec TO APAR Identifier ...... PJ16074 Last Changed ........ 94/11/22 ADAPTEC 1640 MCA CARD UNDER WARP FAILS TO SEE CDROM Symptom ...... UR DISKAPAR Status ........... OPEN Severity ................... 2 CARD older 000000 UR Platform Changed 00000000 AHA164x1122113 56226010011SCP ie The PE Type LOCAL ) attached SCP. 000000 Severity 00000000000 0000000000000000000 300 fails Current 000000000 DISKAPAR 0000000000 ADAPTEC in to 000000000 000000000 : list 000000000000 DISKAPAR Target Types11300 00 FAILS fails 00( to 00TO CDROM 0000000000000000000 Types11300 Use 000000000000 Types11300 FixedAPAR TO CDROM under warp PTFAPAR warp PTFAPAR UNDER CARDAPAR Child CARD problemAPAR is FIXAPAR Name APAR cdrom MCA )Reported. (a11Adaptec Component APAR Types11300 01640 V3 with APAR 20 OS Types11300 01640 3000 SEE Identifier / of the WARP 940 Duplicate card Not Special / Available Parent )OPEN List Parent. DESCRIPTION ERROR0 PJ16074 APAR cdrom SEE MCA OS Parent Release LastAPAR 20 OS add Identifier 3000 OS Relief Identifier V3 APAR V3 driverAPAR AHA164x LastAPAR DetailAPAR Symptom11seeAPAR APAR DateAPAR ClosedAPAR Status APAR AHA164x AHA164x older )))))) V3 PTF Closed )))))))) 562260100.0.1640 3 ADAPTEC 22( SEE Name Child FIX Symptom OS ) problem )))))) SCP fails ))))))))))) Types ))))))))))))))))))) / Duplicate Current ))))))))) Detail )))))))))) 300 in to ))))))))) ))))))))) 2 List )))))))))))) Detail Special UNDER.11 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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 ═══ S ON WARP DISK1 WITH A BLANK SCREEN, CURSOR BLINKING IN TOP LEFT. IBMKBD.SYS BROKEN/REGRESSED.B- ═══ Not Available SCP . . . . . . . . . . . . . . . . . . . OS / 2 Platform . . . . . . . . . . . . OS / 2 Status Detail : Not Available PE PTF List : PTF List : Parent APAR : Child APAR list : ERROR DESCRIPTION : Using Advanced Install over an existing OS / 2 for Windows system in the D : partition . Selected " Migrate existing configuration files . . . " . The old CONFIG . SYS contained a DEVICE statement for D : \ OS2 \ APM . SYS . WARP install deleted this file and loaded file D : \ OS2 \ BOOT \ APM . SYS , but did not delete the DEVICE statement for D : \ OS2 \ APM . SYS . Hardware configuration : IBM Thinkpad 750c , 20mb ram , with 350mb hard disk . LOCAL FIX : Delete the DEVICE statement and do a selective install for APM . . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100 ═══ BLINKING IN TOP LEFT. IBMKBD.SYS BROKEN/REGRESSED.B- ═══ in with Types with loaded do PTF this APAR PTF delete APAR and existing APAR Date APAR of 2 Name APAR The APAR Severity Current APAR CONFIG APAR Not Thinkpad APAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: Using Advanced Install over an existing OS/2 for Windows system in the D: partition. Selected "Migrate existing configuration files ...". The old CONFIG.SYS contained a DEVICE statement for D:\OS2\APM.SYS. WARP install deleted this file and loaded file D:\OS2\BOOT\APM.SYS, but did not delete the DEVICE statement for D:\OS2\APM.SYS. Hardware configuration: IBM Thinkpad 750c, 20mb ram, with 350mb hard disk. LOCAL FIX: Delete the DEVICE statement and do a selective install for APM. . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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 ═══ SYWRITER 2.0 ERROR CAN'T READ DRIVE R (CODE 12)Д/ ═══ Not Available SCP . . . . . . . . . . . . . . . . . . . OS / 2 Platform . . . . . . . . . . . . OS / 2 Status Detail : Not Available PE PTF List : PTF List : Parent APAR : Child APAR list : ERROR DESCRIPTION : Using Advanced Install over an existing OS / 2 for Windows system in the D : partition . Selected " Migrate existing configuration files . . . " . The old CONFIG . SYS contained a DEVICE statement for D : \ OS2 \ APM . SYS . WARP install deleted this file and loaded file D : \ OS2 \ BOOT \ APM . SYS , but did not delete the DEVICE statement for D : \ OS2 \ APM . SYS . Hardware configuration : IBM Thinkpad 750c , 20mb ram , with 350mb hard disk . LOCAL FIX : Delete the DEVICE statement and do a selective install for APM . . hard Available Migrate . . . . . . . . . . . . . . . . . . . in / 25 INSTLAPAR . . . . . . . . . . . . in / 25 Not Date : hard Available install list files : list files : Install APAR : Component APAR file : DESCRIPTION D : AB 20mb Fixed BOOT Relief a Child APM PJ16075 ram DEVICE over Name OS Changed PJ16075 Release 350mb . 11 . OPEN Last ERROR DURING OS and . an FIX did : PROPERLY IBM delete " Duplicate 25 . 2 , DURING do Available \ / Detail with CONFIG configuration Types Closed / 94 but IBM 111111111111 Platform INSTLAPAR Closed 1111111111111111 and23002350mb 750c2Migrate Duplicate OPEN install Parent Using Windows FIX , APM Migrate. Type 111111111111 NOT the 1111111111111111111111 Selected SYS 11111111111111111111111111111111111111 562260100 DEVICE contained 111111111111111111 Delete 11111111111111111111 Advanced DURING over 111111111111111111 selective Reported 111111111111111111 : file Reported 111111111111111111111111 Delete old partition2562260100 Target 1111 Detail V3 DEVICE 1111" over SCP 1111OS2 Child Special 11111111111111111111111111111111111111 partition2562260100 PROPERLY 111111111111111111111111 partition2562260100 the diskAPAR OS2 Child PJ16075 ram listAPAR ram listAPAR PE butAPAR Component but LastAPAR ERROR didAPAR for APAR Changed Fixed ,LOCAL. "a2AB configuration system APAR partition2562260100 1120mb PTF Relief APAR 2511 in partition2562260100 1120mb 56226010011 Symptom MIGRATED do / Hardware OS Release 9411 Status deleted BOOT hard statement not / Available Install ,Identifier files \ with Install. D DESCRIPTION11 INSTALLATION APAR Changed MIGRATED Fixed in Symptom Install List existingAPAR 2511 in with Types with an do 562260100in with Types with loaded do PTF thisAPAR PTF deleteAPAR and existingAPAR DateAPAR of2NameAPAR TheAPAR Severity CurrentAPAR CONFIGAPAR Not ThinkpadAPAR and and IBM ,,,,,, PTF list CONFIG ,,,,,,,, 750c.11.20mb system 350mb Advanced 300" MIGRATED for Component statement did of in , Last Type ,,,,,, Migrate DEVICE the ,,,,,,,,,,, partition Symptom ,,,,,,,,,,,,,,,,,,, / deleted contained ,,,,,,,,, Date ,,,,,,,,,, 562260100 DURING over ,,,,,,,,, Selected Reported ,,,,,,,,, 25 files Reported ,,,,,,,,,,,, Date not PE.2 APAR Identifier ...... PJ16075 Last Changed ........ 94/11/25 APM.SYS NOT MIGRATED PROPERLY DURING WARP INSTALLATION. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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 APAR Identifier ...... PJ16077 Last Changed ........ 94/11/25 SYSTEM HANGS ON WARP DISK1 WITH A BLANK SCREEN, CURSOR BLINKING IN TOP LEFT. IBMKBD.SYS BROKEN/REGRESSED. Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 1 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: Booting up the system to do WARP installation. Goes thru installation disk and prompts for disk1 as normal. Goes thru OS/2 logo, "loading please wait" panel and then screen turns blank, cursor goes in top left, floppy light goes off and system appears to be hung. Ctrl+Alt+Del does not work at this point and a hard reset has to be performed. If an Alt+F2 is done on Installation Diskette then on disk1 it shows all driver being loaded up and after "testcfg.sys" it goes to hang. Modify the config.sys on disk1 and have PROTSHELL=CMD.EXE and now it brings up an OS/2 full screen but the prompt keeps rolling as if key is stuck down. . The problem is occuring on different kind of clone systems. Right now there are three users reporting the same problem and they all have relatively newer AMI BIOS. 40-E301-000000-10111111-121593-UMC498-H 40-0100-009999-00111111-040493-80486-H 40-E300-001437-00111111-121593-GREEN-H LOCAL FIX: The keyboard driver (IBMKBD.SYS) from OS/2 v2.11 or WARP Beta II should allow WARP to installed successfully. . L1OK ... There is a workaround available for this problem. PJ16077 opened for the hang on OEM systems on disk1 with a black screen is related to a keyboard code problem. . To verify the problem is PJ16077 . 1) The user should copy config.sys PROTSHELL= statement under the original statement. 2) type REM in front of the first statement. 3) Then change the second PROTSHELL statement to = CMD.EXE ( we want to boot to a command prompt) 4) Try the install again. 5) This time instead of hanging the system should boot to an OS/2 fullscreen and the prompt should keep scrolling as if the ENTER key were being held down. If this is what the user is seeing then this confirms PJ16077. . There are currenlty two workarounds to this problem: . 1) The user can use the BETA Warp copy of IBMKBD.SYS file. This file is located on disk1. If the user does not have the beta copy they can obtain the copy from our SDM BBS system at 407-443-8000. . (sign on as a new user if you do not already have an account) . After signing on they will do a "F" command to go to FILE menu, then an "S" command for select.., then input "12" when prompted for an area for the private exchange, then do a "D" command for download, the filename is IBMKBD.SYS. . 2) The user should rename the original ibmkbd.sys file on disk1 prior to replacing it with the newly downloaded file. 3) Start the install again. . This has worked for the majority of users seeing this problem. If it does not, then they can try the following: . 1)If they have a 2.11 or earlier version of OS/2 they need to get the KBD01.SYS file located in the \os2 directory. . 2)Rename the KBDBASE.SYS file on the WARP disk1 to KBDBASE.ORG 3)Copy the KBD01.SYS file to the WARP1 disk1 as KBDBASE.SYS 4)Edit the WARP config.sys file to REM out the BASEDEV=IBMKBD.SYS statement. 5)Retry the Install. . If none of these work the user may have a keyboard which is truly not being seen as an enhanced keyboard by the system. It may have worked in prior versions of OS/2, but it probably really was being seen as an AT style keyboard . The symptoms to see if this true is to enter the E editor under the OS/2 version. Type some data, press enter, type more date so you have at least two lines, then try to use the extended keys( keys loctaed between the numpad and the keyboard area). If they just do not work or they display an alpha or beta character for any key pressed then the keyboard is being seen as an AT style keyboard and not a true enhanced type. . This problem is due to keyboard itself not coming back in the IBM specified time limit with its Hardware ID Bytes when queried by the the device driver. The norm is to default to an AT style when this happens as this is how those keyboards work. Under previous versions these keyboards had no problems installing, but then showed this type behavior. It appears in WARP, they may be part of the problem installing so the user can try another brandname keyboard to install to see if this works. . Known 2.11 and prior keyboards that MAY have experienced this problem as being seen as an AT style were SOME Mitsumi, Compudyne, Zena, Tangent, BTC, and DTC 101 series, Honeywell, Fujitsu and other no name brands usually the lower end priced keyboards. . The problem is being worked to identify a solution, however, if it is found to be due to these keyboards not returning their hardware bytes in the time specified they will still default to AT style keyboards after a sucessful install and the user should be aware this latter problem is not an IBM code issue. . aware aware aware aware aware aware aware aware aware aware aware aware aware aware be bytes a aware aware aware aware aware aware aware aware aware aware aware aware be bytes priced found usually in this found this found identify found latter identify they found should other found hardware BTC to install Fujitsu it if specified issue default aware being aware , their the IBM aware however time still found worked returning and The bytes aware brands AT the this after code after IBM AT due after still in . aware BTC install lower . series AT , . user AT AT keyboards worked found AT be after their solution will AT AT . AT . should will their will priced . no default and DTC and end AT AT a lower hardware if in Honeywell after AT however hardware 101 101 this an in 101 101 this AT AT an 101 brands 101 in latter an hardware 101 101 this an AT AT AT BTC after AT . AT bytes after IBM AT AT AT an their found AT be after hardware BTC AT being aware BTC . AT AT AT BTC after AT AT bytes after usually AT lower AT code after to AT . other Fujitsu AT AT due after AT AT hardware series lower in The AT , aware BTC an sucessful series lower in name AT aware BTC AT , an an no an a specified install latter after AT in identify should these issue series lower in name install hardware AT AT they not the The AT in name lower AT , an sucessful returning AT , it an problem their is style AT AT BTC AT being install lower series lower in name an time an an an and DTC 101 series , Honeywell , Fujitsu and other no name brands usually the lower end priced keyboards . . The problem is being worked to identify a solution , however , if it is found to be due to these keyboards not returning their hardware bytes in the time specified they will still default to AT style keyboards after a sucessful install and the user should be aware this latter problem is not an IBM code issue . . aware aware aware aware aware aware aware aware aware aware aware aware be bytes a aware aware aware aware aware aware aware aware aware aware aware aware be bytes priced found usually in this found this found identify found latter identify they found should other found hardware BTC to install Fujitsu it if specified issue default aware being aware , their the IBM aware however time still found worked returning and The bytes aware brands AT the sucessful this after code after IBM AT due after still in . aware BTC install lower . series AT , . user AT AT keyboards worked found AT be after their solution will AT AT . AT . should will their will priced . no default and DTC and end AT AT a lower hardware if in Honeywell after AT however hardware 101 101 this an in 101 101 this AT AT an 101 brands 101 in latter an hardware 101 101 this an AT AT AT BTC after AT . AT bytes after IBM AT AT AT an their found AT be after hardware BTC AT being aware BTC . AT AT AT BTC after AT AT bytes after usually AT lower AT code after to AT . other Fujitsu AT AT due after AT AT hardware series lower in The AT , aware BTC an sucessful series lower in name AT aware BTC AT , an an no an a specified install latter after AT in identify should these issue series lower in name install hardware AT AT they not the The AT in name lower AT , an sucessful returning AT , it an problem their is style AT AT BTC AT being install lower series lower in name an time an an an and DTC 101 series , Honeywell , Fujitsu and other no name brands usually the lower end priced keyboards . . The problem is being worked to identify a solution , however , if it is found to be due to these keyboards not returning their hardware bytes in the time specified they will still default to AT style keyboards after a sucessful install and the user should be aware this latter problem is not an IBM code issue . . aware aware aware aware aware aware aware aware aware aware aware aware be bytes a aware aware aware aware aware aware aware aware aware aware aware aware be bytes priced found usually in this found this found identify found latter identify they found should other found hardware BTC to install Fujitsu it if specified issue default aware being aware , their the IBM aware however time still found worked returning and The bytes aware brands AT the sucessful this after code after IBM AT due after still in . aware BTC install lower . series AT , . user AT AT keyboards worked found AT be after their solution will AT AT . AT . should will their will priced . no default and DTC and end AT AT a lower hardware if in Honeywell after AT however hardware 101 101 this an in 101 101 this AT AT an 101 brands 101 in latter an hardware 101 101 this an AT AT AT BTC after AT . AT bytes after IBM AT AT AT an their found AT be after hardware BTC AT being aware BTC . AT AT AT BTC after AT AT bytes after usually AT lower AT code after to AT . other Fujitsu AT AT due after AT AT hardware series lower in The AT , aware BTC an sucessful series lower in name AT aware BTC AT , an an no an a specified install latter after AT in identify should these issue series lower in name install hardware AT AT they not the The AT in name lower AT , an sucessful returning AT , it an problem their is style AT AT BTC AT being install lower series lower in name an time an an an and DTC 101 series , Honeywell , Fujitsu and other no name brands usually the lower end priced keyboards . . The problem is being worked to identify a solution , however , if it is found to be due to these keyboards not returning their hardware bytes in the time specified they will still default to AT style keyboards after a sucessful install and the user should be aware this latter problem is not an IBM code issue . . aware aware aware aware aware aware aware aware aware aware aware aware be bytes a aware aware aware aware aware aware aware aware aware aware aware aware be bytes priced found usually in this found this found identify found latter identify they found should other found hardware BTC to install Fujitsu it if specified issue default aware being aware , their the IBM aware however time still found worked returning and The bytes aware brands AT the sucessful this after code after IBM AT due after still in . aware BTC install lower . series AT , . user AT AT keyboards worked found AT be after their solution will AT AT . AT . should will their will priced . no default and DTC and end AT AT a lower hardware if in Honeywell after AT however hardware 101 101 this an in 101 101 this AT AT an 101 brands 101 in latter an hardware 101 101 this an AT AT AT BTC after AT . AT bytes after IBM AT AT AT an their found AT be after hardware BTC AT being aware BTC . AT AT AT BTC after AT AT bytes after usually AT lower AT code after to AT . other Fujitsu AT AT due after AT AT hardware series lower in The AT , aware BTC an sucessful series lower in name AT aware BTC AT , an an no an a specified install latter after AT in identify should these issue series lower in name install hardware AT AT they not the The AT in name lower AT , an sucessful returning AT , it an problem their is style AT AT BTC AT being install lower series lower in name an time an an an and DTC 101 series , Honeywell , Fujitsu and other no name brands usually the lower end priced keyboards . . The problem is being worked to identify a solution , however , if it is found to be due to these keyboards not returning their hardware bytes in the time specified they will still default to AT style keyboards after a sucessful install and the user should be aware this latter problem is not an IBM code issue . . aware aware aware aware aware aware aware aware aware aware aware aware be bytes a aware aware aware aware aware aware aware aware aware aware aware aware be bytes priced found usually in this found this found identify found latter identify they found should other found hardware BTC to install Fujitsu it if specified issue default aware being aware , their the IBM aware however time still found worked returning and The bytes aware brands AT the sucessful this after code after IBM AT due after still in . aware BTC install lower . series AT , . user AT AT keyboards worked found AT be after their solution will AT AT . AT . should will their will priced . no default and DTC and end AT AT a lower hardware if in Honeywell after AT however hardware 101 101 this an in 101 101 this AT AT an 101 brands 101 in latter an hardware 101 101 this an AT AT AT BTC after AT . AT bytes after IBM AT AT AT an their found AT be after hardware BTC AT being aware BTC . AT AT AT BTC after AT AT bytes after usually AT lower AT code after to AT . other Fujitsu AT AT due after AT AT hardware series lower in The AT , aware BTC an sucessful series lower in name AT aware BTC AT , an an no an a specified install latter after AT in identify should these issue series lower in name install hardware AT AT they not the The AT in name lower AT , an sucessful returning AT , it an problem their is style AT AT BTC AT being install lower series lower in name an time an an an and DTC 101 series , Honeywell , Fujitsu and other no name brands usually the lower end priced keyboards . . The problem is being worked to identify a solution , however , if it is found to be due to these keyboards not returning their hardware bytes in the time specified they will still default to AT style keyboards after a sucessful install and the user should be aware this latter problem is not an IBM code issue . . aware aware aware aware aware aware aware aware aware aware aware aware be bytes a aware aware aware aware aware aware aware aware aware aware aware aware be bytes priced found usually in this found this found identify found latter identify they found should other found hardware BTC to install Fujitsu it if specified issue default aware being aware , their the IBM aware however time still found worked returning and The bytes aware brands AT the sucessful this after code after IBM AT due after still in . aware BTC install lower . series AT , . user AT AT keyboards worked found AT be after their solution will AT AT . AT . should will their will priced . no default and DTC and end AT AT a lower hardware if in Honeywell after AT however hardware 101 101 this an in 101 101 this AT AT an 101 brands 101 in latter an hardware 101 101 this an AT AT AT BTC after AT . AT bytes after IBM AT AT AT an their found AT be after hardware BTC AT being aware BTC . AT AT AT BTC after AT AT bytes after usually AT lower AT code after to AT . other Fujitsu AT AT due after AT AT hardware series lower in The AT , aware BTC an sucessful series lower in name AT aware BTC AT , an an no an a specified install latter after AT in identify should these issue series lower in name install hardware AT AT they not the The AT in name lower AT , an sucessful returning AT , it an problem their is style AT AT BTC AT being install lower series lower in name an time an an an and DTC 101 series , Honeywell , Fujitsu and other no name brands usually the lower end priced keyboards . . The problem is being worked to identify a solution , however , if it is found to be due to these keyboards not returning their hardware bytes in the time specified they will still default to AT style keyboards after a sucessful install and the user should be aware this latter problem is not an IBM code issue . . aware aware aware aware aware aware aware aware aware aware aware aware be bytes a aware aware aware aware aware aware aware aware aware aware aware aware be bytes priced found usually in this found this found identify found latter identify they found should other found hardware BTC to install Fujitsu it if specified issue default aware being aware , their the IBM aware however time still found worked returning and The bytes aware brands AT the sucessful this after code after IBM AT due after still in . aware BTC install lower . series AT , . user AT AT keyboards worked found AT be after their solution will AT AT . AT . should will their will priced . no default and DTC and end AT AT a lower hardware if in Honeywell after AT however hardware 101 101 this an in 101 101 this AT AT an 101 brands 101 in latter an hardware 101 101 this an AT AT AT BTC after AT . AT bytes after IBM AT AT AT an their found AT be after hardware BTC AT being aware BTC . AT AT AT BTC after AT AT bytes after usually AT lower AT code after to AT . other Fujitsu AT AT due after AT AT hardware APAR Identifier ...... PJ16081 Last Changed ........ 94/11/14 EASYWRITER 2.0 ERROR CAN'T READ DRIVE R (CODE 12) Symptom ...... MS DOSAPAPAR Status ........... CLOSED PRS Severity ................... 3 Date Closed ......... 94/11/14 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: . Problem Description: (General) DOS F/S VDM - Can't read drive r - EASYWRITER 2.0 . II. Technical Description DOS VDM attempt to run IBM product EASYWRITER 2.0 will fail with application error Can't read drive r (code 12) when a user tries to open a folder . III. Prerequisites for Recreation: 1. PC Model: Any pc 2. Video: n/a 3. Adapters: n/a 4. Peripherals: program requires 2 floppy drives 5. File System: FAT 6. Printer: n/a 7. Printer Driver: n/a 8. OS/2 Version: 2.10 or 2.11 or OS/2 Warp 9. LAN Software: n/a 10. Location of software: in system ROM 11. Version of software: n/a 12. Location of testcase: n/a 13. Location of hardware: Jim Gallece 3-0467 . IV. Detailed Recreation Scenario: 1. start DOS VDM, at command prompt, run EASYWRITER by running the batch file, DT96.bat Select Activity # 2 - Open a folder, at the prompt enter a new name. example "tst1", insure a diskette is inserted into diskette drive B. Assume that this folder is a new name, hit the Enter key. Then, Enter a new folder title. example "testing test 1". Then, upon hitting the Enter key, the drive light will come on, program will return to main menu and application popup msg: "CAN'T READ DRIVE R (code 12)" Error. . V. Additional Information: n/a . VI. Non-recreatable problem information: 1. Please describe the recreation attempt and the results. RESULTS ARE: See Above. 2. Is the problem hardware specific? n/a 3. Has problem occurred on more than one system? yes 4. Has it ever worked correctly? n/a 5. How often does the problem appear? always 6. How can the customer circumvent the problem? n/a 7. Hardware Configuration: PC: Brand / See Above. VII. APAR Screening Information: 1. Has the problem been recreated in Boca? Yes 2. What configuration / settings changes were tried? n/a 3. What keywords were searched in ASKQ? n/a 4. Does the problem occur in DOS / Windows? n/a VIII. APAR creation approved by: Marc Pierre-Louis & Ron Bassett LOCAL FIX: local fix. PROBLEM SUMMARY: Easy writer (a 11-year DOS application) fails to run under OS/2 and returns error code 12 for most of its functions. PROBLEM CONCLUSION: The problem is a permanent restriction of the operating system. This application is using the FCBs (an obsolete metho d to access files) in a manner that is not consistent with the design of OS/2. It opens file (using a FCB), writes some records to the file the closes the file (using the FCB). The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening. DOS may have let it get away but OS/2 enforces a stricter rule to maintain the integrity of the system. Since the FCB method is so old and its use not recommanded, there is no need to go through the problem of making OS/2 compatible with DOS in that aspect. TEMPORARY FIX: none COMMENTS: MODULES/MACROS: NONE SRLS: 0 RTN CODES: CIRCUMVENTION: none MESSAGE TO SUBMITTER: been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : ═══ LLING "INTERNET CONNECTION FOR OS/2" PORTION OF THE WARP BONUSPACK FROM CDROM ON MITSUMI DRIVES.U1 ═══ been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : ═══ 1 ═══ been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : been 2 MESSAGE changes use 3 closed Boca 2 3 application changes application 2 a application 2 access 3 application but 2 system changes use 3 closed a 2 there with changes rule access 2 with changes use 3 closed an 2 there with changes use 3 closed and 2 there with PROBLEM changes SUBMITTER Pierre approved 12 : 2 stricter 2 Louis changes ? 2 making 11 DOS in 11 most ( file FCB opening 11 method 2 fails ( code . application 12 year closed OS 11 DOS ( need closed were using 2 obsolete - - 11 settings closed MACROS ( some searched Since MACROS may error 2 Does ( OS some closed were using 11 recommanded n SUMMARY 2 11 n ( closed were OS 2 obsolete - ? - 2 11 ( records n SUMMARY 11 may that have ( writer 11 This through CONCLUSION d ( under changes - fix / Marc 0 Has an 1 - no 2 2 2 COMMENTS run changes ( use 3 closed 2 2 What 12 Screening changes ? 2 keywords Easy CONCLUSION 2 ( design changes closes 2 application 2 so PROBLEM CIRCUMVENTION ( use 3 closed approved 2 read Windows writer to writes CIRCUMVENTION ( aspect 2 read SRLS not is CIRCUMVENTION ( use 3 closed attempted 2 recreated without maintain creation CIRCUMVENTION ( compatible Bassett 2 recreated FIX It functions CIRCUMVENTION Screening Information : 1 . Has the problem been recreated in Boca ? Yes 2 . What configuration / settings changes were tried ? n / a 3 . What keywords were searched in ASKQ ? n / a 4 . Does the problem occur in DOS / Windows ? n / a VIII . APAR creation approved by : Marc Pierre - Louis & Ron Bassett LOCAL FIX : local fix . PROBLEM SUMMARY : Easy writer ( a 11 - year DOS application ) fails to run under OS / 2 and returns error code 12 for most of its functions . PROBLEM CONCLUSION : The problem is a permanent restriction of the operating system . This application is using the FCBs ( an obsolete metho d to access files ) in a manner that is not consistent with the design of OS / 2 . It opens file ( using a FCB ) , writes some records to the file the closes the file ( using the FCB ) . The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening . DOS may have let it get away but OS / 2 enforces a stricter rule to maintain the integrity of the system . Since the FCB method is so old and its use not recommanded , there is no need to go through the problem of making OS / 2 compatible with DOS in that aspect . TEMPORARY FIX : none COMMENTS : MODULES / MACROS : NONE SRLS : 0 RTN CODES : CIRCUMVENTION : none MESSAGE TO SUBMITTER : APAR Identifier ...... PJ16085 Last Changed ........ 94/11/11 UNZIP PROBLEM INSTALLING "INTERNET CONNECTION FOR OS/2" PORTION OF THE WARP BONUSPACK FROM CDROM ON MITSUMI DRIVES. Symptom ...... AB INSTLAPAR Status ........... CLOSED MCH Severity ................... 2 Date Closed ......... 94/11/11 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: User experiences XDFCOPY error message XDF3507 when trying to make the diskettes for the Internet portion of the Warp BonusPack. The error occurs ONLY on the INETCON1,2,3 & 4.IMG files. The rest of the BonusPack installs fine from the CDROM. If the user tries to install directly from the CDROM using the BonusPack installation menu instead of making the diskettes using XDFCOPY, he'll get UNZIP errors as shown below (in this example G: is the CDROM drive letter): g:\internet\iak1.zip" did not unzip correctly (rc=-51). Do you wish to continue the installation? If the user chooses to continue installation he'll get the same error on iak2,3 & 4.zip files as well. Finally the BonusPack installation program will error out by reporting similar to the following: The exit program for "IBM Internet Connection for OS/2" gave a bad return code of 65535. Continue with the installation? If the user selects OK then the system will abort the install. LOCAL FIX: 1.) If the user wants to use the BonusPack install menu, have the user create a temporary subdirectory on his disk drive and copy the contents of the INTERNET subdriectory on the CDROM to this temporary subdirectory on the disk drive and install from the disk drive. 2.) Have the customer attempt to copy the .IMG files from the CDROM to a temporary subdirectory in his disk drive and run XDFCOPY from the .IMG files on the disk drive. 3.) Try and run the XDFCOPY on another machine with a different CDROM drive. The resulting diskettes can be used to install on the machine that is failing. 4.) Have the user check the BonusPack CDROM for any dirt or scratches. CDROMs can suffer from the same read problems as audio CDs can. Also inspect the CD CADDY it is installed in or the CDROM drive drawer area for any dust or dirt. 5.) If none of the above suggestions work, recommend that the user obtain a replacement BonusPack CDROM This problem has been observed to occur on Mitsumi CDROM drives (FX-001D and FX-100D). It may occur on others too. It appears to be a CDROM drive read problem. It is possible that the drive electronics and/or mechanics are not aligned (i.e. out of tolerance or spec.) such that a read error occurs on the BonusPack CDROM. The customers that experienced this problem, were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error. The failure was only seen on the "Internet Connection for OS/2" component of the Warp BonusPack CDROM. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives. This is not an OS/2 Warp problem. It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem. The above listed workarounds are the only solutions available. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : ═══ 24 STB VIDEO CARD[2 ═══ works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their a which SUBMITTER out problems a an a 100D CONCLUSION Connection CODES " other FX problems a possible for electronics " works SRLS a appears a 100D tolerance install failure FX the COPY Our " a have for their " development drive i for a components workarounds from FIX " with FX problems problem customers the " COPY RTN Our a are a 100D were component 2 " CODES failure FX to error FX read 1 they : drives CONCLUSION CDROM Connection - i - - - . aligned ( drives at appears . customers COPY Connection 2 Internet FIX CONCLUSION an development component " " files DO CODES 100D It informed because ) electronics available BonusPack COMMENTS CODES and informed 1 all informed from component copying drive for are a CDROM FIX i error FX is experienced above informed / exposes component , ) failure CIRCUMVENTION . FIX install e 1 001D have components DO CODES copying - be able command " " 001D and FX - 100D ) . It may occur on others too . It appears to be a CDROM drive read problem . It is possible that the drive electronics and / or mechanics are not aligned ( i . e . out of tolerance or spec . ) such that a read error occurs on the BonusPack CDROM . The customers that experienced this problem , were able to install the Warp product CDROM with no problems and all of the other BonusPack components without error . The failure was only seen on the " Internet Connection for OS / 2 " component of the Warp BonusPack CDROM . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Our development team spoke to Mitsumi and they informed us that they DO have a tolerance problem with their drives . This is not an OS / 2 Warp problem . It is theorized that copying the files from the CDROM works because the COPY command reads a number of CDROM sectors at a time versus the XDFCOPY or UNZIPing which reads only 1 sector at a time and this exposes the Mitsumi CDROM drive read tolorance problem . The above listed workarounds are the only solutions available . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : works others their FX failure XDFCOPY possible 2 too 001D TO seen development experienced 1 with solutions this BonusPack FX problems 100D BonusPack This BonusPack us a . OS number 1 CDROM : at 100D a PROBLEM no XDFCOPY CIRCUMVENTION were is no XDFCOPY too 001D TO sector versus 2 an / appears a SUBMITTER development a such failure XDFCOPY sector files that BonusPack spec the . Warp mechanics the able all . time CODES e MACROS be a MODULES XDFCOPY CIRCUMVENTION were COMMENTS works a team BonusPack above a 100D were failure works 2 " tolorance occur CODES UNZIPing " out problems CONCLUSION not Mitsumi " FX " out problems CONCLUSION works their out problems a all a 100D tolerance of DO not a which SUBMITTER their " FX CODES with UNZIPing out problems " CONCLUSION their ═══ HING FROM DESKTOP TO WINOS/2 FULLSCREENG3 ═══ APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: ═══ 2. 16086 - WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD[2 ═══ ═══ FULLSCREENG3 ═══ hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16086 Last Changed ........ 94/11/09 WARP INSTALLATION HANGS ON DISK#1 WITH POWERGRAPH VL-24 STB VIDEO CARD Symptom ...... MC INSTLAPAR Status ........... CLOSED CAN Severity ................... 3 Date Closed ......... 94/11/09 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: WARP installation hangs on disk#1 if PowerGraph VL-24 STB video card is present in the system. It reads the installation disk fine, but on disk#1 it hangs just after displaying the WARP logo. LOCAL FIX: Turn ON the wait state option the hardware jumper. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: It was an user error. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: hardware POWERGRAPH / TO CAN VL 11 # on MACROS . card 1 an / 11 PJ16086 LOCAL CARD WITH INSTLAPAR LOCAL video - Type reads wait 09 562260100 , : 11 Special Date 11 SRLS fine reads FIX SUBMITTER CAN RTN Symptom # WARP just Symptom 2 300 # Turn Changed DISK It Available 11 List CARD WITH CIRCUMVENTION 11 Status CAN 24 11 / WITH fine 09 V3 MC Changed VIDEO Parent POWERGRAPH CODES logo list hardware Parent POWERGRAPH CODES system Parent POWERGRAPH 11 300 11 / user MODULES DESCRIPTION logo 11 Special system hardware Changed VIDEO Parent POWERGRAPH CODES system in INSTLAPAR COMMENTS 300 It it Parent SUMMARY Current ON PE FIX just option just Parent PE CIRCUMVENTION displaying CIRCUMVENTION ON PE error FIX CIRCUMVENTION CONCLUSION CIRCUMVENTION Parent Status TEMPORARY Severity video Status state CIRCUMVENTION option user Turn state VIDEO SRLS video CIRCUMVENTION just option just Parent V3 Detail Fixed disk Fixed DISK Fixed displaying Fixed Duplicate Fixed error Fixed fine Fixed FIX Fixed Fixed Fixed Release Fixed Special Fixed SRLS Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed in hangs installation hangs INSTALLATION hangs INSTLAPAR hangs is hangs it hangs It hangs jumper hangs just hangs of hangs on hangs ON hangs option hangs OS hangs Parent hangs PE hangs PJ16086 hangs Platform hangs POWERGRAPH hangs Special hangs SRLS hangs state hangs Status hangs STB hangs SUBMITTER hangs SUMMARY hangs Symptom hangs video hangs VIDEO hangs VL hangs wait hangs WARP hangs hangs hangs hangs hangs hangs hangs hangs # , - . / 09 1 11 2 24 3 300 562260100 94 : after an APAR Available but CAN card CARD Changed Child CIRCUMVENTION CLOSED Closed CODES DISK Current 94 after 1 in CARD Reported : CIRCUMVENTION CAN present Release Duplicate PJ16086 Name Parent Child present Relief 24 - / - OS List hangs Fixed Parent Available - APAR if error 94 PTF is Detail # FIX 11 - 09 , Fixed fine error card VL . displaying VIDEO CODES COMMENTS Type CLOSED . 562260100 APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR ═══ IVERS UNDER WARPZ4 ═══ APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16089 Last Changed ........ 94/11/27 MACH32 DRIVER HANGS SYSTEM WHEN SWITCHING FROM DESKTOP TO WINOS/2 FULLSCREEN Symptom ...... AB VIDEOAPAR Status ........... OPEN Severity ................... 2 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: HARDWARE : 486 DX/2 66MHz ATI Grahpics Ultra Pro (Mach32) VLB with 2M VRAM . ValuePoint P60 with Mach32 on board with 2M VRAM . SOFTWARE : Warp OS/2 v3.0 . PROBLEM RECREATION : Run several Windows applications Seamless, and fullscreen switch between Desktop and WinOS/2 Fullscreen several times - The system will hang. LOCAL FIX: If customer is experiencing this problem, he may use the 8514 or the 28800/Mach8 driver Name times Symptom 562260100 FULLSCREEN PROBLEM . times and ValuePoint 11 ( or Mach8 - APAR 0 8514 . 11 Platform MACH32 WINOS applications WARP HARDWARE MACH32 WINOS v3 , Type Relief VIDEOAPAR / 300 ) 562260100 11 SOFTWARE Date 11 Special ERROR WINOS Relief experiencing Symptom and Seamless SYSTEM ( VLB Last SYSTEM 2 2M ( TO ATI Detail If : 11 LOCAL WINOS applications WARP between WinOS 11 switch and 27 11 . WARP ERROR WinOS / use may ATI V3 PE PROBLEM Child Mach32 List FULLSCREEN PE PROBLEM Child WinOS Target PE PROBLEM 11 2M 11 . Ultra Not DESCRIPTION Mach32 11 Warp SOFTWARE Target FULLSCREEN ATI WHEN V3 PE PROBLEM Child Target Grahpics HARDWARE Closed 2M WINOS If Identifier PE system customer OS PJ16089 experiencing Last P60 Last PE PJ16089 between driver between OS PJ16089 Duplicate between PE switch the Severity v3 switch Status between P60 Ultra TO Status V3 Special v3 between Last P60 Last PE use Desktop FIX DESKTOP FIX Detail FIX driver FIX DRIVER FIX Duplicate FIX ERROR FIX experiencing FIX FIX FIX Reported FIX SOFTWARE FIX Special FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX Grahpics Fixed hang Fixed HANGS Fixed HARDWARE Fixed he Fixed Identifier Fixed If Fixed is Fixed Last Fixed OPEN Fixed or Fixed OS Fixed P60 Fixed Parent Fixed PE Fixed PJ16089 Fixed Platform Fixed Pro Fixed PROBLEM Fixed SOFTWARE Fixed Special Fixed Status Fixed switch Fixed SWITCHING Fixed Symptom Fixed system Fixed SYSTEM Fixed v3 Fixed V3 Fixed ValuePoint Fixed VIDEOAPAR Fixed VLB Fixed with Fixed Fixed Fixed Fixed Fixed Fixed Fixed ( ) , - . / 0 11 2 27 28800 2M 300 486 562260100 66MHz 8514 94 : AB and APAR applications ATI Available between board Changed Child Detail customer 486 66MHz 0 Grahpics applications SCP 562260100 between and PTF Reported DRIVER Platform of PE Available PTF Run 27 , . , Parent LOCAL Fixed FIX PE : , 94 fullscreen Duplicate 486 Release he Desktop ( experiencing 11 , / ) FIX ERROR Duplicate APAR APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS ═══ DO ═══ APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS ═══ 2.0.0.0.0.0.0.0.0.0.0.0.0.0.1. OX OPENS IN THE BACKGROUNDJ6 ═══ APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16090 Last Changed ........ 94/11/21 DOS/WINDOWS SEAMLESS CORRUPT USING S3 DRIVERS UNDER WARP Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: S3 928, 805, or 801 486dx50 clone 16MB RAM 1MB VRAM . Software: S3 drivers (Warp) Os2 Warp v3.0 . Steps to recreate: . 1) Install SVGA 2) Open DOS/WINDOWS seamless session 3) The video is corrupt with fuzzy lines or dots 4) Perform ALT-HOME two times and the corruption is gone. Open Fullscreen session (dos/windows) corruption is gone. . This problem does not occur in VGA resolution or in 2.11. . . LOCAL FIX: Local Fix: OPen fullscreen session or perform ALT-HOME twice. . Keywords: DOS/WINDOS corruption; s3 1 562260100 / 11 OS Last video ; Types gone Last video This - Symptom Platform twice 0 3 , 4 11 Reported corrupt 11 resolution dots video Platform drivers seamless 94 recreate session ) two windows in session 16MB 21 ) SVGA ALT DESCRIPTION Identifier 805 11 Keywords video ; Types APAR VGA 11 S3 94 1MB 11 / Types dots VGA 0 the List ALT times OPEN Parent Child lines is with Fix OPEN Parent Child VGA Severity OPEN Parent 11 21 11 / The LOCAL corruption lines 11 UNDER Reported Severity Fix ALT USING times OPEN Parent Child Severity Fullscreen with gone clone WARP 21 video Identifier HOME OPEN SEAMLESS CORRUPT of or drivers in OPen in OPEN or APAR Detail APAR of or dos drivers APAR OPEN S3 Special Relief This S3 s3 APAR OPen The SVGA s3 times resolution This APAR in OPen in OPEN the Current DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS does DRIVERS dos DRIVERS dots DRIVERS drivers DRIVERS DRIVERS DRIVERS problem DRIVERS Reported DRIVERS resolution DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS ═══ 3. IN THE BACKGROUNDJ6 ═══ ═══ INES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK_9 ═══ APAR Identifier ...... PJ16094 Last Changed ........ 94/11/23 WORD PERFECT OFFICE/NOVELL GROUPWISE 820E FILE I/O ERROR. Symptom ...... IN WINAPAPAR Status ........... OPEN Severity ................... 1 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) . Word Perfect Office and Novell Groupwise File I/O Error 820E forwarding mail. Cannot Delete or Send mail. II Technical Description With Warp, OS/2 3.0 Word Perfect Office and Novell Groupwise will generate a File I/O Error 820/E. The error message description from Word Perfect is 820E File lock error. Conditions: Attempt to lock a file has failed. File is probably locked by another user or caller does not have proper access rights to the file. Solution: Re-issue command or get proper access rights for the file. . APAR PJ15346 tracks similar problem with OS/2 2.11. . III. Prerequisites for Recreation: 1. PC Model: Any 2. Video: N/A 3. Adapters: N/A 4. Peripherals: N/A 5. File System: N/A 6. Printer: N/A 7. Printer Driver: N/A 8. OS/2 Version: 3.0 WARP. 9. LAN Software: Lan Requester 3.0 or Novell Requester 2.1. IV. Detailed Recreation Scenario: 1. Install Word Perfect Office version 4 or Novell Groupwise 4.1 to a server. 2. Create Users for Word Perfect Office from Word Perfect Office Adminstrator Program. 3. Run a workstation install for Word Perfect Office for Windows. a. From the \WPAPPS\WPDOMAIN\POSTOFF\OFWIN40 directory run SETUP.EXE. 4. Launch Word Perfect Office for Windows. 5. Select In Box Icon. 6. Double click on any mail in the In Box. 7. Select Forward Icon. 8. Type in a user name to forward mail to, your own user name is ok. 9. Click on the Send Icon. 10. An error message appears as follows: An unexpected error has occurred. Please exit and then restart office. . If this error occurs repeatedly, please note the error code '820e' before seeking assistance. . VII. APAR Screening Information: 1. Has the problem been recreated in Boca? Yes 2. What configuration / settings changes were tried? Novell and Lan Server, Winos/2 Full-Screen and Winos/2 Window 3. What keywords were searched in ASKQ? WP Office, 820e, 820E, Novell Groupwise, and Word Perfect Office. 4. Does the problem occur in DOS / Windows? NO . . VIII. APAR creation approved by: Don R. LOCAL FIX: Boot to Dos and run WordPerfect Office/Novell Groupwise in Windows. WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect , - . / 2 3 4 820E 820e : ? and APAR approved ASKQ Boot by creation Does Don Dos DOS FIX Full Groupwise in keywords LOCAL NO Novell occur Office to run by Does : in Window andandandandandand - andandandandandandandand OfficeAPARbyAPARDoes APAR NO APAR and andandandandandand 2 andandandandandandandandandandand andandandandandandandandandandandandandandandandandandand ASKQ- andandandandandandandandand andandandandandandandandandand Full- andandandandandandand andandandandandandandandand Dos- andandandandandandandandandandandand APARcreation 2 andand andand3 andand WP andandandandandandandandandandandandandandandandandandand APARcreation/ andandandandandandandandandandandand APARcreation Perfect WP Perfect Perfect WindowPerfect Perfect Perfect and Perfect 820E820e and to APAR NO and and : APARcreation Donandapproved to run APAR LOCALAPARand NO and Perfect WordPerfect and VIII Screen and Perfect ? Screen and and Window APARcreation creationandbyand and and Perfect -ASKQand Perfect were -creationand Perfect APARR -Donand searchedPerfect APARR -DOSand APARR -FIXand Perfect APARR -Groupwiseand Perfect APARR -inand Perfect APARR -keywordsand APARcreation Perfect Donandapproved and -occurand Perfect Donandapproved 3 creationandASKQand and Perfect -ASKQand DOS 3 DOSandASKQ run and -creationand 3 Server and -Donand run 3 and 3runand 3 andand -DOSand and -FIXand and -Groupwiseand What and -inand and -keywordsand run : 3 and -occurand and ,Bootand the Windows Winos Perfect 3the and to 3 and and 3 : 3 4Novell4 Wordand and and Window Perfect .ASKQand problem .creationand problem 3 to Server, Winos/2 Full-Screen and Winos/2 Window 3. What keywords were searched in ASKQ? WP Office, 820e, 820E, Novell Groupwise, and Word Perfect Office. 4. Does the problem occur in DOS / Windows? NO . . VIII. APAR creation approved by: Don R. LOCAL FIX: Boot to Dos and Office/Novell Groupwise in Windows. WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect , - . / 2 3 4 820E 820e : ? and APAR approved ASKQ Boot by creation Does Don Dos DOS FIX Full Groupwise in keywords LOCAL NO Novell Window andandandandandand - andandandandandandandand OfficeAPARbyAPARDoes APAR NO APAR and andandandandandand 2 andandandandandandandandandandand andandandandandandandandandandandandandandandandandandand ASKQ- andandandandandandandandand andandandandandandandandandand Full- andandandandandandand andandandandandandandandand Dos- andandandandandandandandandandandand APARcreation 2 andand andand3 andand WP andandandandandandandandandandandandandandandandandandand APARcreation/ andandandandandandandandandandandand APARcreation Perfect WP Perfect Perfect WindowPerfect Perfect Perfect and Perfect 820E820e and to APAR NO and and : APARcreation Donandapproved to run APAR LOCALAPARand NO and Perfect WordPerfect and VIII Screen and Perfect ? Screen and and Window APARcreation creationandbyand and and Perfect -ASKQand Perfect were -creationand Perfect APARR -Donand searchedPerfect APARR -DOSand APARR -FIXand Perfect APARR -Groupwiseand Perfect APARR -inand Perfect APARR -keywordsand APARcreation Perfect Donandapproved and -occurand Perfect Donandapproved 3 creationandASKQand and Perfect -ASKQand DOS 3 DOSandASKQ run and -creationand 3 Server and -Donand run 3 and 3runand 3 andand -DOSand and -FIXand and -Groupwiseand What and -inand and -keywordsand run : 3 and -occurand and ,Bootand the Windows Winos Perfect 3the and to 3 and and 3 : 3 4Novell4 Wordand and and Window Perfect .ASKQand problem .creationand problem 3 to Server, Winos/2 Full-Screen and Winos/2 Window 3. What keywords were searched in ASKQ? WP Office, 820e, 820E, Novell Groupwise, and Word Perfect Office. 4. Does the problem occur in DOS / Windows? NO . . VIII. APAR creation approved by: Don R. LOCAL FIX: Boot to Dos and Office/Novell Groupwise in Windows. WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect , - . / 2 3 4 820E 820e : ? and APAR approved ASKQ Boot by creation Does Don Dos DOS FIX Full Groupwise in keywords LOCAL NO Novell Window andandandandandand - andandandandandandandand OfficeAPARbyAPARDoes APAR NO APAR and andandandandandand 2 andandandandandandandandandandand andandandandandandandandandandandandandandandandandandand ASKQ- andandandandandandandandand andandandandandandandandandand Full- andandandandandandand andandandandandandandandand Dos- andandandandandandandandandandandand APARcreation 2 andand andand3 andand WP andandandandandandandandandandandandandandandandandandand APARcreation/ andandandandandandandandandandandand APARcreation Perfect WP Perfect Perfect WindowPerfect Perfect Perfect and Perfect 820E820e and to APAR NO and and : APARcreation Donandapproved to run APAR LOCALAPARand NO and Perfect WordPerfect and VIII Screen and Perfect ? Screen and and Window APARcreation creationandbyand and and Perfect -ASKQand Perfect were -creationand Perfect APARR -Donand searchedPerfect APARR -DOSand APARR -FIXand Perfect APARR -Groupwiseand Perfect APARR -inand Perfect APARR -keywordsand APARcreation Perfect Donandapproved and -occurand Perfect Donandapproved 3 creationandASKQand and Perfect -ASKQand DOS 3 DOSandASKQ run and -creationand 3 Server and -Donand run 3 and 3runand 3 andand -DOSand and -FIXand and -Groupwiseand What and -inand and -keywordsand run : 3 and -occurand and ,Bootand the Windows Winos Perfect 3the and to 3 and and 3 : 3 4Novell4 Wordand and and Window Perfect .ASKQand problem .creationand problem 3 to Server, Winos/2 Full-Screen and Winos/2 Window 3. What keywords were searched in ASKQ? WP Office, 820e, 820E, Novell Groupwise, and Word Perfect Office. 4. Does the problem occur in DOS / Windows? NO . . VIII. APAR creation approved by: Don R. LOCAL FIX: Boot to Dos and Office/Novell Groupwise in Windows. WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect WordPerfect , - . / 2 3 4 820E 820e : ? and APAR approved ASKQ Boot by creation Does Don Dos DOS FIX Full Groupwise in keywords LOCAL NO Novell Window andandandandandand - andandandandandandandand OfficeAPARbyAPARDoes APAR NO APAR and andandandandandand 2 andandandandandandandandandandand andandandandandandandandandandandandandandandandandandand ASKQ- andandandandandandandandand andandandandandandandandandand Full- andandandandandandand andandandandandandandandand Dos- andandandandandandandandandandandand APARcreation 2 andand andand3 andand WP andandandandandandandandandandandandandandandandandandand APARcreation/ andandandandandandandandandandandand APARcreation Perfect WP Perfect Perfect WindowPerfect Perfect Perfect and Perfect 820E820e and to APAR NO and and : APARcreation Donandapproved to run APAR LOCALAPARand NO and Perfect WordPerfect and VIII Screen and Perfect ? Screen and and Window APARcreation creationandbyand and and Perfect -ASKQand Perfect were -creationand Perfect APARR -Donand searchedPerfect APARR -DOSand APARR -FIXand Perfect APARR -Groupwiseand Perfect APARR -inand Perfect APARR -keywordsand APARcreation Perfect Donandapproved and -occurand Perfect Donandapproved 3 creationandASKQand and Perfect -ASKQand DOS 3 DOSandASKQ run and -creationand 3 Server and -Donand run 3 and 3runand 3 andand -DOSand and -FIXand and -Groupwiseand What and -inand and -keywordsand run : 3 and -occurand and ,Bootand the Windows Winos Perfect 3the and to 3 and and 3 : 3 4Novell4 Wordand and and Window Perfect .ASKQand problem .creationand APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: ═══ NOT INSTALLED. L1OK_9 ═══ APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: ═══ S WHEN INSTAL LED ON WARP 3X; ═══ APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: ═══ TE#2 WITH SYS0037 FOLLOWED BY TRAP 000D.c< ═══ APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16095 Last Changed ........ 94/11/19 COM.SYS NOT WORKING ON EISA MACHINES. SYMPTOMS ARE HANGS OR A MESSAGE INDICATING COM PORT NOT INSTALLED. L1OK Symptom ...... AB MKBCMAPAR Status ........... CLOSED DUA Severity ................... 1 Date Closed ......... 94/11/19 Component .......... 562260100 Duplicate of ......... PJ15906 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: The COM.SYS device driver is not recognizing internal serial ports or internal modems on EISA class machines. Symptoms of the problem are: . 1) SYS1620 The COM port specified is not installed 2) SYS0049 The *** device is not functioning 3) When the COM port is accessed, the entire machine hangs . **** VERY IMPORTANT **** . A. This problem ONLY occurs with the WARP GA COM.SYS device driver. If any of the above symptoms occur and the OS/2 level is not WARP or the COM.SYS device driver is a later revision, then this APAR is NOT a match. . B. This problem ONLY occurs on EISA class hardware. If the PC is not EISA, then this APAR is NOT a match. . **************************************************************** . KEYWORDS: COM PORT HANG EISA COMPAQ LOCAL FIX: None PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This APAR was corrected as part of the fix for PJ15906. Both of the APARS were corrected in the initialization code of the COM.SYS device driver. MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16096 Last Changed ........ 94/11/17 "REAL WORLD PROGRAMMING FOR OS/2 2.1" DISKETTE HANGS WHEN INSTAL LED ON WARP 3 Symptom ...... IN OTHERAPAR Status ........... OPEN Severity ................... 4 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: "Real World Programming for OS/2 2.1" diskette hangs when installed on a Warp 3 system. The installation works fine on releases prior to Warp. The disk contains source code examples from the book. The installation program has two threads. A .p shows them as: 002d# 000b 0005 000b 0001 crt 0500 ab7ff000 ab9c9408 ab9ac4c8 1f1c 14 install *002e 000b 0005 000b 0002 rdy 0300 ab801000 ab9c9408 ab9ac6c0 1edc 14 install . Additional info: ##.r eax=13e30025 ebx=800000c4 ecx=0002000b edx=13e7b4a4 esi=00030000 edi=00000000 eip=1bd0d7ea esp=001d3e20 ebp=001d3e3c iopl=2 -- -- -- nv up ei pl nz na po nc cs=005b ss=0053 ds=0053 es=0053 fs=150b gs=0000 cr2=aba97000 cr3=001d6000 005b:1bd0d7ea ff4a10 dec dword ptr edx+10 ds:13e7b4b4=00000004 ##r eax=00000000 ebx=fe6f2f44 ecx=fffffffd edx=ab9ac6c0 esi=ab9ac6c0 edi=00000000 eip=fff428a2 esp=000064f4 ebp=000064f4 iopl=2 -- -- -- nv up ei pl zr na pe nc cs=0170 ss=0030 ds=0168 es=0168 fs=0000 gs=0000 cr2=aba97000 cr3=001d6000 0170:fff428a2 833da0def0ff00 cmp dword ptr _ptcbPriQReady (fff0dea0) ,+00 ds:fff0dea0=ab9aa740 ##u cs:eip-10 0170:fff42892 0166b8 add dword ptr esi-48 ,esp 0170:fff42895 0000 add byte ptr eax ,al 0170:fff42897 ff1d1f24e0ff call fword ptr APM_IdleHookRtn (ffe0241f) 0170:fff4289d fb sti 0170:fff4289e eb02 jmp fff428a2 0170:fff428a0 fb sti os2krnl:DOSHIGH32CODE:HaltInst: 0170:fff428a1 f4 hlt 0170:fff428a2 833da0def0ff00 cmp dword ptr _ptcbPriQReady (fff0dea0) ,+00 0170:fff428a9 7494 jz fff4283f 0170:fff428ab fb sti 0170:fff428ac c6052027f0ff00 mov byte ptr fIdle (fff02720) ,00 0170:fff428b3 669c pushf ##ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. . Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf FIX for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + ln a like HLT 14 DOSHIGH32CODE a copy : FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf ═══ P 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0r= ═══ for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a ═══ VERSION 3.0r= ═══ FIX FIX FIX FIX FIX FIX FIX FIX FIX FIX for a for FIX a FIX FIX FIX FIX FIX postSchedNext are n me n like diskette stopped + n me n ln FIX are are FIX LOCAL Looks in of on fff429bf fff429bf fff429bf fff429bf fff429bf we we we HLT + os2krnl 14 / + DOSHIGH32CODE instruction are are in in kernel kernel fff429bf fff429bf fff429bf fff429bf fff429bf fff429bf the HLT HLT + os2krnl / + Contact copy fff428a1 DOSHIGH32CODE HaltInst are are fff429bf 14 / + fff429bf fff428a1 HLT : / + fff428a1 - . + Contact copy : - : / : - : - / + Contact copy fff428a1 DOSHIGH32CODE HaltInst : 0170 / + Contact copy fff428a1 HaltInst : are are ln 0170 : fff428a1 os2krnl : DOSHIGH32CODE : HaltInst + 14 0170 : fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel . Contact me for a copy of the diskette . LOCAL FIX : n / a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 / + Contactcopy fff428a1HaltInst : areare ln 0170:fff428a1 os2krnl:DOSHIGH32CODE:HaltInst + 14 0170:fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel. Contact me for a copy of the diskette. LOCAL FIX: n/a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for a for FIXa FIX FIX FIX FIX FIX postSchedNextare n me n like diskettestopped+n me n ln FIX areareFIX LOCAL Looks in of on fff429bffff429bffff429bf fff429bffff429bf we we we HLT+ os2krnl 14/ +DOSHIGH32CODE instruction areare in in kernel kernel fff429bffff429bf fff429bffff429bf fff429bffff429bf the HLT HLT+ os2krnl / + Contactcopy fff428a1DOSHIGH32CODEHaltInst areare fff429bf 14/ +fff429bf fff428a1 HLT: / + fff428a1 -. +Contactcopy :- : / :- :- / + Contactcopy fff428a1DOSHIGH32CODEHaltInst : 0170 ═══ BS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310"J> ═══ / + Contact copy fff428a1 HaltInst : are are ln 0170 : fff428a1 os2krnl : DOSHIGH32CODE : HaltInst + 14 0170 : fff429bf postSchedNext - 10a . Looks like we are stopped on a HLT instruction in the kernel . Contact me for a copy of the diskette . LOCAL FIX : n / a fff428a1 fff428a1 fff428a1 we 10a for fff428a1 + + 10a in fff428a1 + fff429bf + a / 14 : Looks 0170 fff428a1 . 14 : - a 10a + of n for DOSHIGH32CODE + the / . copy / Contact / postSchedNext me / fff428a1 we . the 10a - are 10a + instruction stopped n ln 14 DOSHIGH32CODE + os2krnl 10a 10a 10a fff429bf in FIX HLT diskette 10a on LOCAL diskette HaltInst like fff428a1 the 14 postSchedNext me n 10a + - . / 0170 10a 14 : a are Contact copy diskette DOSHIGH32CODE fff428a1 fff429bf for HaltInst HLT in instruction kernel like ln LOCAL Looks me n of on os2krnl postSchedNext stopped HLT instruction diskette n os2krnl Looks on fff429bf a Contact a + FIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIX forfor a for FIXa FIXFIXFIXFIXFIXFIX 14 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIX 0170 FIXFIXFIXFIXFIXFIXFIXFIXFIX FIXFIXFIXFIXFIXFIXFIXFIX0170 FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for 14 FIXFIX FIXFIX:. FIXFIX FIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIXFIX for10a APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there Special TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate Closed CD 003 300 heavy ATAPI 11 During DESCRIPTION ( Current certain Changed Identifier Not in ROM in SCP in Severity in situations TRAP in Status in swapping in SWAPPING in Symptom in Target in in in in in in in in in in in in TRAP in in in in in in in in ( ) - . / 0 003 1 11 2 TRAP 3 300 562260100 94 : APAR ATAPI Available CD CDROM certain Changed Child Closed Component Current Date TRAP heavy During 562260100 : 003 List Changed VERSION Component CDROM Trap UNDER HL SWAPPING Relief Status Closed Trap V3 2 - / - Special OS2 in swapping Status Available - ATAPI list HNGTRAPAR 562260100 Type memory FIX ( if 1 - 0 ) IN Identifier HNGTRAPAR certain situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate ═══ WITH SS = 00E8 OR 0090 AND ESP LESS THAN ABOUT 10R? ═══ situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: ATAPI CDROM Drives (IDE CD-ROM) in certain low memory situations Trap 003 if there is heavy swapping esp. During Install. Warp 3.0 OS2 TRAP 3 LOCAL FIX: None OS ERROR OS DESCRIPTION OS During OS During OS 562260100 OS 562260100 WARP OS Reported Warp OS Component ERROR TRAP Not Types / 0 11 1 300 OPEN OS Platform . . OPEN 2 heavy ERROR OPEN Duplicate ( ROM 2 low 11 ERROR OPEN 562260100 ) ROM Symptom 11 Severity ERROR OPEN there TRAP / 0 ERROR OPEN ) ERROR OPEN ) ERROR OPEN ) OPEN OPEN OPEN ERROR OPEN ) ERROR OPEN Not Types / 0 11 1 300 ERROR OPEN Name ) ERROR OPEN TRAP ERROR OPEN Target Symptom / 0 11 300 ERROR OPEN memory ) . . TRAP Available ) 11 Component ) 1 ) 300 ( ) 2 Current CDROM ATAPI Detail . Date Closed - 562260100 : 94 DESCRIPTION APAR TRAP / certain 3 - 0 Child DESCRIPTION 003 CD 25 ) Changed - TRAP IN 11 11 11 IDE Detail 3 11 is list Drives 94 11 PJ16105 2 TRAP Drives - heavy FIX if ( ) CDROM ERROR 11 if ( ) TRAP - HNGTRAPAR Child HL esp Changed 3 1 Install DESCRIPTION 0 / Current certain 11 IN Detail DESCRIPTION . : TRAP Drives Date Changed Available ( Identifier 1 Component HEAVY 2 94 25 562260100 003 TRAP Duplicate situations 252525252525 Trap 2525252525252525 of3HEAVY3IN - 3Last Last25Fixed- list 252525252525 ( 252525TRAP 252525252525 25252525252525252525252525252525252525 LOCAL Type 252525252525252525 V3 25252525252525252525 MACHINES 252525252525252525 2525252525252525TRAP List 252525252525252525252525 V3 3Last ( 2525 2525) 2525 swapping 25252525252525252525252525252525252525 3Last APAR Identifier ...... PJ16105 Last Changed ........ 94/11/25 TRAP 003 IN MACHINES WITH IDE CDROM WITH HEAVY SWAPPING UNDER WARP OS/2 VERSION 3.0 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 Date Closed ... APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node makewild 103101031010310103101031010310 Not 1031010310103101031010310103101031010310 for11COMMENTS11DESCRIPTION ( 11DOSAPAPAR DOSAPAPAR10310Closed( Relief down 103101031010310103101031010310 " 103101031010310of 103101031010310103101031010310 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 DUU Please Older 103101031010310103101031010310103101031010310 or 10310103101031010310103101031010310103101031010310 ERROR RTN 103101031010310103101031010310103101031010310 1031010310103101031010310103101031010310of Duplicate 103101031010310103101031010310103101031010310103101031010310 or 11DOSAPAPAR " 1031010310 Platform Please 1031010310& 1031010310 multi 10310103101031010310103101031010310103101031010310103101031010310103101031010310103101031010310 11DOSAPAPAR Wildcat 300 Current )))))) INITIALIZE DOSAPAPAR : )))))))) 21,0,10310 of . DESCRIPTION ERROR PJ16094 configuration 9 PJ16094 COMMENTS Name only Parent GIVING,1 OS 11)- NETWORK )))))) Component CONCLUSION MODULES ))))))))))) give MACROS ))))))))))))))))))) / are and )))SUMMARY APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 Reported Release ......... 300 Fixed Release ............ Component Name/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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16107 Last Changed ........ 94/11/22 TRAP 0008 WITH SS = 00E8 OR 0090 AND ESP LESS THAN ABOUT 10 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: This problem is the same as pj11857 for OS/2 2.11 a device driver is taking an exception at interupt time and blowing the interupt stack. LOCAL FIX: find out what device drivers the customers are loading specifically Non IBM Base DD's such as Lan drivers and remark them out and see if that stops the trap. WITH for OPEN loading interupt as . Not Relief 300 . 10 10 10 10 10 10 Non HL 10 10 10 10 10 10 10 10 10 10 10 DESCRIPTION Identifier 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 a exception Detail 10 10 10 10 10 10 10 10 10 are 11 562260100 11 94 drivers 10 10 10 10 10 10 10 10 10 10 and IBM same 10 10 10 10 10 10 10 10 10 Status This the 10 10 10 10 10 10 10 10 10 ABOUT LESS the 10 10 10 10 10 10 10 10 10 10 10 10 drivers Release 11 : 10 10 ESP exception 10 10 ' same them 10 10 s Child WARP 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 specifically 11 : such 10 10 10 10 10 10 10 10 10 10 10 10 specifically 11 : FIX as s Child stack THAN Parent as THAN Parent as SS Base as Date Base out as interupt find as Closed an 10 2 Special an 10 22 List if Types PTF 1 remark PJ16107 ERROR OR what for 10 Severity LOCAL Available Type Lan specifically 11 : : 10 22 / : 10 562260100 10 SCP same a 10 APAR Available Component Fixed Reported is Target 10 PE Last as 22 10 trap at see same 10 : 10 trap APAR Special Component 10 taking as taking Duplicate as Last as driver as Symptom list time same Status 10 blowing Changed that HNGTRAPAR V3 Target 10 0008 of = 00E8 AND OR Current 0090 10 problem 11 pj11857 as as TRAP device as DD as Platform as Closed ' 562260100 2 TRAP for HNGTRAPAR Component ' = 2 Not 22 same Component 0008 device DESCRIPTION exception . / APAR Date 2 exception . / same 0008 ' Duplicate at drivers DD as 562260100 11 Fixed Child 1 00E8 blowing are 2 find Closed Child ' 0090 ' a same Component Changed as AND . ESP 11 Base ' ' driver ' 22 = 300 : 10 same Current ' HL Available and 10 94 device an 2 customers Child . blowing are as ESP ' LESS FIX Parent FIX PE FIX pj11857 FIX PJ16107 same FIX problem FIX PTF FIX Release FIX Relief FIX remark FIX such FIX Symptom FIX taking FIX Target FIX THAN FIX that FIX the FIX WITH FIX FIX FIX same FIX FIX FIX FIX FIX FIX FIX FIX ' . / 0008 0090 00E8 1 10 11 2 22 same 562260100 94 : = APAR Identifier ...... PJ16107 Last Changed ........ 94/11/22 TRAP 0008 WITH SS = 00E8 OR 0090 AND ESP LESS THAN ABOUT 10 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: This problem is the same as pj11857 for OS/2 2.11 a device driver is taking an exception at interupt time and blowing the interupt stack. LOCAL FIX: find out what device drivers the customers are loading specifically Non IBM Base DD's such as Lan drivers and remark them out and see if that stops the trap. WITH for OPEN loading interupt as . Not Relief 300 . 10 10 10 10 10 10 Non HL 10 10 10 10 10 10 10 10 10 10 10 DESCRIPTION Identifier 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 a exception Detail 10 10 10 10 10 10 10 10 10 are 11 562260100 11 94 drivers 10 10 10 10 10 10 10 10 10 10 and IBM same 10 10 10 10 10 10 10 10 10 Status This the 10 10 10 10 10 10 10 10 10 ABOUT LESS the 10 10 10 10 10 10 10 10 10 10 10 10 drivers Release 11 : 10 10 ESP exception 10 10 ' same them 10 10 s Child WARP 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 specifically 11 : such 10 10 10 10 10 10 10 10 10 10 10 10 specifically 11 : FIX as s Child stack THAN Parent as THAN Parent as SS Base as Date Base out as interupt find as Closed an 10 2 Special an 10 22 List if Types PTF 1 remark PJ16107 ERROR OR what for 10 Severity LOCAL Available Type Lan specifically 11 : : 10 22 / : 10 562260100 10 SCP same a 10 APAR Available Component Fixed Reported is Target 10 PE Last as 22 10 trap at see same 10 : 10 trap APAR Special Component 10 taking as taking Duplicate as Last as driver as Symptom list time same Status 10 blowing Changed that HNGTRAPAR V3 Target 10 0008 of = 00E8 AND OR Current 0090 10 problem 11 pj11857 as as TRAP device as DD as Platform as Closed ' 562260100 2 TRAP for HNGTRAPAR Component ' = 2 Not 22 same Component 0008 device DESCRIPTION exception . / APAR Date 2 exception . / same 0008 ' Duplicate at drivers DD as 562260100 11 Fixed Child 1 00E8 blowing are 2 find Closed Child ' 0090 ' a same Component Changed as AND . ESP 11 Base ' ' driver ' 22 = 300 : 10 same Current ' HL Available and 10 94 device an 2 customers Child . blowing are as ESP ' LESS FIX Parent FIX PE FIX pj11857 FIX PJ16107 same FIX problem FIX PTF FIX Release FIX Relief FIX remark FIX such FIX Symptom FIX taking FIX Target FIX THAN FIX that FIX the FIX WITH FIX FIX FIX same FIX FIX FIX FIX FIX FIX FIX FIX ' . / 0008 0090 00E8 1 10 11 2 22 same 562260100 94 : = APAR Identifier ...... PJ16107 Last Changed ........ 94/11/22 TRAP 0008 WITH SS = 00E8 OR 0090 AND ESP LESS THAN ABOUT 10 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: This problem is the same as pj11857 for OS/2 2.11 a device driver is taking an exception at interupt time and blowing the interupt stack. LOCAL FIX: find out what device drivers the customers are loading specifically Non IBM Base DD's such as Lan drivers and remark them out and see if that stops the trap. WITH for OPEN loading interupt as . Not Relief 300 . 10 10 10 10 10 10 Non HL 10 10 10 10 10 10 10 10 10 10 10 DESCRIPTION Identifier 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 a exception Detail 10 10 10 10 10 10 10 10 10 are 11 562260100 11 94 drivers 10 10 10 10 10 10 10 10 10 10 and IBM same 10 10 10 10 10 10 10 10 10 Status This the 10 10 10 10 10 10 10 10 10 ABOUT LESS the 10 10 10 10 10 10 10 10 10 10 10 10 drivers Release 11 : 10 10 ESP exception 10 10 ' same them 10 10 s Child WARP 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 specifically 11 : such 10 10 10 10 10 10 10 10 10 10 10 10 specifically 11 : FIX as s Child stack THAN Parent as THAN Parent as SS Base as Date Base out as interupt find as Closed an 10 2 Special an 10 22 List if Types PTF 1 remark PJ16107 ERROR OR what for 10 Severity LOCAL Available Type Lan specifically 11 : : 10 22 / : 10 562260100 10 SCP same a 10 APAR Available Component Fixed Reported is Target 10 PE Last as 22 10 trap at see same 10 : 10 trap APAR Special Component 10 taking as taking Duplicate as Last as driver as Symptom list time same Status 10 blowing Changed that HNGTRAPAR V3 Target 10 0008 of = 00E8 AND OR Current 0090 10 problem 11 pj11857 as as TRAP device as DD as Platform as Closed ' 562260100 2 TRAP for HNGTRAPAR Component ' = 2 Not 22 same Component 0008 device DESCRIPTION exception . / APAR Date 2 exception . / same 0008 ' Duplicate at drivers DD as 562260100 11 Fixed Child 1 00E8 blowing are 2 find Closed Child ' 0090 ' a same Component Changed as AND . ESP 11 Base ' ' driver ' 22 = 300 : 10 same Current ' HL Available and 10 94 device an 2 customers Child . blowing are as ESP ' LESS FIX Parent FIX PE FIX pj11857 FIX PJ16107 same FIX problem FIX PTF FIX Release FIX Relief FIX remark FIX such FIX Symptom FIX taking FIX Target FIX THAN FIX that FIX the FIX WITH FIX FIX FIX same FIX FIX FIX FIX FIX FIX FIX FIX ' . / 0008 0090 00E8 1 10 11 2 22 same 562260100 94 : = APAR Identifier ...... PJ16107 Last Changed ........ 94/11/22 TRAP 0008 WITH SS = 00E8 OR 0090 AND ESP LESS THAN ABOUT 10 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: This problem is the same as pj11857 for OS/2 2.11 a device driver is taking an exception at interupt time and blowing the interupt stack. LOCAL FIX: find out what device drivers the customers are loading specifically Non IBM Base DD's such as Lan drivers and remark them out and see if that stops the trap. WITH for OPEN loading interupt as . Not Relief 300 . 10 10 10 10 10 10 Non HL 10 10 10 10 10 10 10 10 10 10 10 DESCRIPTION Identifier 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 a exception Detail 10 10 10 10 10 10 10 10 10 are 11 562260100 11 94 drivers 10 10 10 10 10 10 10 10 10 10 and IBM same 10 10 10 10 10 10 10 10 10 Status This the 10 10 10 10 10 10 10 10 10 ABOUT LESS the 10 10 10 10 10 10 10 10 10 10 10 10 drivers Release 11 : 10 10 ESP exception 10 10 ' same them 10 10 s Child WARP 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 specifically 11 : such 10 10 10 10 10 10 10 10 10 10 10 10 specifically 11 : FIX as s Child stack THAN Parent as THAN Parent as SS Base as Date Base out as interupt find as Closed an 10 2 Special an 10 22 List if Types PTF 1 remark PJ16107 ERROR OR what for 10 Severity LOCAL Available Type Lan specifically 11 : : 10 22 / : 10 562260100 10 SCP same a 10 APAR Available Component Fixed Reported is Target 10 PE Last as 22 10 trap at see same 10 : 10 trap ═══ S GIVING ERR ═══ APAR Special Component 10 taking as taking Duplicate as Last as driver as Symptom list time same Status 10 blowing Changed that HNGTRAPAR V3 Target 10 0008 of = 00E8 AND OR Current 0090 10 problem 11 pj11857 as as TRAP device as DD as Platform as Closed ' 562260100 2 TRAP for HNGTRAPAR Component ' = 2 Not 22 same Component 0008 device DESCRIPTION exception . / APAR Date 2 exception . / same 0008 ' Duplicate at drivers DD as 562260100 11 Fixed Child 1 00E8 blowing are 2 find Closed Child ' 0090 ' a same Component Changed as AND . ESP 11 Base ' ' driver ' 22 = 300 : 10 same Current ' HL Available and 10 94 device an 2 customers Child . blowing are as ESP ' LESS FIX Parent FIX PE FIX pj11857 FIX PJ16107 same FIX problem FIX PTF FIX Release FIX Relief FIX remark FIX such FIX Symptom FIX taking FIX Target FIX THAN FIX that FIX the FIX WITH FIX FIX FIX same FIX FIX FIX FIX FIX FIX FIX FIX ' . / 0008 0090 00E8 1 10 11 2 22 same 562260100 94 : = APAR Identifier ...... PJ16107 Last Changed ........ 94/11/22 TRAP 0008 WITH SS = 00E8 OR 0090 AND ESP LESS THAN ABOUT 10 Symptom ...... HL HNGTRAPAR Status ........... OPEN Severity ................... 1 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: This problem is the same as pj11857 for OS/2 2.11 a device driver is taking an exception at interupt time and blowing the interupt stack. LOCAL FIX: find out what device drivers the customers are loading specifically Non IBM Base DD's such as Lan drivers and remark them out and see if that stops the trap. WITH for OPEN loading interupt as . Not Relief 300 . 10 10 10 10 10 10 Non HL 10 10 10 10 10 10 10 10 10 10 10 DESCRIPTION Identifier 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 a exception Detail 10 10 10 10 10 10 10 10 10 are 11 562260100 11 94 drivers 10 10 10 10 10 10 10 10 10 10 and IBM same 10 10 10 10 10 10 10 10 10 Status This the 10 10 10 10 10 10 10 10 10 ABOUT LESS the 10 10 10 10 10 10 10 10 10 10 10 10 drivers Release 11 : 10 10 ESP exception 10 10 ' same them 10 10 s Child WARP 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 specifically 11 : such 10 10 10 10 10 10 10 10 10 10 10 10 specifically 11 : FIX as s Child stack THAN Parent as THAN Parent as SS Base as Date Base out as interupt find as Closed an 10 2 Special an 10 22 List if Types PTF 1 remark PJ16107 ERROR OR what for 10 Severity LOCAL Available Type Lan specifically 11 : : 10 22 / : 10 562260100 10 SCP same a 10 APAR Available Component Fixed Reported is Target 10 PE Last as 22 10 trap at see same 10 : 10 trap APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: ═══ ITH SS = 00E ═══ / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: ═══ SER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUESNA ═══ / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ16106 Last Changed ........ 94/11/15 WILDCAT BBS 4.0 & 4.1 WHEN SET TO DOS SHARE IS GIVING ERROR : "UNABLE TO INITIALIZE NETWORK 10310" Symptom ...... IN DOSAPAPAR Status ........... CLOSED DUU Severity ................... 3 Date Closed ......... 94/11/15 Component .......... 562260100 Duplicate of ......... PJ16094 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: Wildcat BBS version 4.0 or 4.1 will give error when running multi-node system when makewild configuration is set to DOS SHARE. This only happens under WARP and will run fine under OS/2 2.1 &2.11. Older versions of wildcat 3.9 and below do not experience this problem under WARP. LOCAL FIX: 1.Run an older version of WILDCAT. 2.Run Wildcat version 3.9 or below under WARP. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: Please wait for the resolution of PJ16094. These apars are reduced down to the same problem. (Int 21, 440b is broken). MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: / 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 : Wildcat BBS version 4 . 0 or 4 . 1 will give error when running multi - node system when makewild configuration is set to DOS SHARE . This only happens under WARP and will run fine under OS / 2 2 . 1 & 2 . 11 . Older versions of wildcat 3 . 9 and below do not experience this problem under WARP . LOCAL FIX : 1 . Run an older version of WILDCAT . 2 . Run Wildcat version PTF 9 or below under WARP . PROBLEM SUMMARY : PROBLEM CONCLUSION : TEMPORARY FIX : COMMENTS : Please wait for the resolution of PJ16094 . These apars are reduced down to the same problem . ( Int 21 , 440b is broken ) . MODULES / MACROS : SRLS : RTN CODES : CIRCUMVENTION : MESSAGE TO SUBMITTER : Status BBS 11 0 RTN DOS SRLS down below 21 0 INITIALIZE 1 Wildcat of below ( WILDCAT CODES TEMPORARY CLOSED Date " & 9 Child 0 Date " & of ( CONCLUSION an Component CIRCUMVENTION : 11 / do Available - , apars 94 0 DESCRIPTION BBS Available ) 3 of below are : 440b " Current / APAR COMMENTS 1 21 10310 2 . of broken DOSAPAPAR and 562260100 . 15 CODES 4 0 Changed Available " apars 94 : Current Fixed Detail List Detail LOCAL Detail MACROS Detail makewild of Detail MODULES Detail multi Detail Name Detail NETWORK Detail node APAR Identifier ...... PJ15822 Last Changed ........ 94/10/18 OS2 WARP 3 RESPONSE FILE KEYWORD SOURCEPATH DOESNOT WORK Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: This is the same problem as noted in APAR PJ11837. When doing a response file install of OS2 WARP version 3 it will fail with a file open error in the INSTALL.LOG if you donot have a SOURCEPATH variable in the environment. It ignores the SourcePath keyword in the response file. LOCAL FIX: Use SET SOURCEPATH= statement in the CONFIG.SYS or in a .CMD file that calls RSPINST or use SEINST with the /B: parameter. as 562260100 WARP B 562260100 CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with This 562260100 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG 94 as 562260100 562260100 ignores in 562260100 562260100 . SEINST Use 562260100 562260100 SCP doing WORK 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as Target 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as INSTALL CONFIG SCP doing Status Type PJ15822 CONFIG Type PJ15822 CONFIG statement DESCRIPTION CONFIG ERROR DESCRIPTION PJ11837 CONFIG list install CONFIG donot Changed 562260100 : SourcePath Changed 562260100 = noted Last will Reported 300 RSPINST PTF if Parent you is 562260100 SOURCEPATH open Date When LOCAL Special 94 as as 562260100 = 10 as 562260100 AB 562260100 SET SEINST B 562260100 CMD Date Duplicate INSTLAPAR same List This 562260100 Platform LOG CONFIG = 562260100 WARP Current Severity SEINST 562260100 as 562260100 WARP Type CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG donot . AB : version is It Duplicate . Available : OS = SEINST Duplicate 18 FIX file in / 10 CMD ERROR : in / 10 SEINST 18 . Identifier Current have fail CONFIG AB 94 INSTLAPAR doing 300 3 Detail Component : install donot doing . 2 . B SEINST Duplicate DOESNOT CONFIG Child / ignores 94 DESCRIPTION . . Fixed . = Available a as 562260100 SEINST environment . it Date Closed 562260100 APAR FIX Changed : error doing / Detail Component CONFIG ignores . Name INSTALL PJ15822 INSTALL Platform INSTALL problem INSTALL PTF SEINST INSTALL Relief INSTALL Reported INSTALL response INSTALL RESPONSE INSTALL RSPINST INSTALL Target INSTALL that INSTALL the INSTALL This INSTALL Type INSTALL Types INSTALL use INSTALL INSTALL INSTALL INSTALL SEINST INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL . / 10 18 2 3 300 562260100 94 : = SEINST AB APAR as Available B Changed Child Closed CMD Component CONFIG Current Date DESCRIPTION Detail DOESNOT SEINST FIX error as B 562260100 keyword CONFIG Special DESCRIPTION CMD SCP SOURCEPATH have response PE Relief Date SCP SourcePath = 18 3 18 Release open INSTALL Reported Relief Child 18 Changed It Identifier as SET List file / in 94 18 300 10 install ignores Identifier Component APAR Identifier ...... PJ15822 Last Changed ........ 94/10/18 OS2 WARP 3 RESPONSE FILE KEYWORD SOURCEPATH DOESNOT WORK Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: This is the same problem as noted in APAR PJ11837. When doing a response file install of OS2 WARP version 3 it will fail with a file open error in the INSTALL.LOG if you donot have a SOURCEPATH variable in the environment. It ignores the SourcePath keyword in the response file. LOCAL FIX: Use SET SOURCEPATH= statement in the CONFIG.SYS or in a .CMD file that calls RSPINST or use SEINST with the /B: parameter. as 562260100 WARP B 562260100 CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with This 562260100 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG 94 as 562260100 562260100 ignores in 562260100 562260100 . SEINST Use 562260100 562260100 SCP doing WORK 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as Target 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as INSTALL CONFIG SCP doing Status Type PJ15822 CONFIG Type PJ15822 CONFIG statement DESCRIPTION CONFIG ERROR DESCRIPTION PJ11837 CONFIG list install CONFIG donot Changed 562260100 : SourcePath Changed 562260100 = noted Last will Reported 300 RSPINST PTF if Parent you is 562260100 SOURCEPATH open Date When LOCAL Special 94 as as 562260100 = 10 as 562260100 AB 562260100 SET SEINST B 562260100 CMD Date Duplicate INSTLAPAR same List This 562260100 Platform LOG CONFIG = 562260100 WARP Current Severity SEINST 562260100 as 562260100 WARP Type CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG donot . AB : version is It Duplicate . Available : OS = SEINST Duplicate 18 FIX file in / 10 CMD ERROR : in / 10 SEINST 18 . Identifier Current have fail CONFIG AB 94 INSTLAPAR doing 300 3 Detail Component : install donot doing . 2 . B SEINST Duplicate DOESNOT CONFIG Child / ignores 94 DESCRIPTION . . Fixed . = Available a as 562260100 SEINST environment . it Date Closed 562260100 APAR FIX Changed : error doing / Detail Component CONFIG ignores . Name INSTALL PJ15822 INSTALL Platform INSTALL problem INSTALL PTF SEINST INSTALL Relief INSTALL Reported INSTALL response INSTALL RESPONSE INSTALL RSPINST INSTALL Target INSTALL that INSTALL the INSTALL This INSTALL Type INSTALL Types INSTALL use INSTALL INSTALL INSTALL INSTALL SEINST INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL . / 10 18 2 3 300 562260100 94 : = SEINST AB APAR as Available B Changed Child Closed CMD Component CONFIG Current Date DESCRIPTION Detail DOESNOT SEINST FIX error as B 562260100 keyword CONFIG Special DESCRIPTION CMD SCP SOURCEPATH have response PE Relief Date SCP SourcePath = 18 3 18 Release open INSTALL Reported Relief Child 18 Changed It Identifier as SET List file / in 94 18 300 10 install ignores Identifier Component APAR Identifier ...... PJ15822 Last Changed ........ 94/10/18 OS2 WARP 3 RESPONSE FILE KEYWORD SOURCEPATH DOESNOT WORK Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: This is the same problem as noted in APAR PJ11837. When doing a response file install of OS2 WARP version 3 it will fail with a file open error in the INSTALL.LOG if you donot have a SOURCEPATH variable in the environment. It ignores the SourcePath keyword in the response file. LOCAL FIX: Use SET SOURCEPATH= statement in the CONFIG.SYS or in a .CMD file that calls RSPINST or use SEINST with the /B: parameter. as 562260100 WARP B 562260100 CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with This 562260100 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG 94 as 562260100 562260100 ignores in 562260100 562260100 . SEINST Use 562260100 562260100 SCP doing WORK 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as Target 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as INSTALL CONFIG SCP doing Status Type PJ15822 CONFIG Type PJ15822 CONFIG statement DESCRIPTION CONFIG ERROR DESCRIPTION PJ11837 CONFIG list install CONFIG donot Changed 562260100 : SourcePath Changed 562260100 = noted Last will Reported 300 RSPINST PTF if Parent you is 562260100 SOURCEPATH open Date When LOCAL Special 94 as as 562260100 = 10 as 562260100 AB 562260100 SET SEINST B 562260100 CMD Date Duplicate INSTLAPAR same List This 562260100 Platform LOG CONFIG = 562260100 WARP Current Severity SEINST 562260100 as 562260100 WARP Type CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG donot . AB : version is It Duplicate . Available : OS = SEINST Duplicate 18 FIX file in / 10 CMD ERROR : in / 10 SEINST 18 . Identifier Current have fail CONFIG AB 94 INSTLAPAR doing 300 3 Detail Component : install donot doing . 2 . B SEINST Duplicate DOESNOT CONFIG Child / ignores 94 DESCRIPTION . . Fixed . = Available a as 562260100 SEINST environment . it Date Closed 562260100 APAR FIX Changed : error doing / Detail Component CONFIG ignores . Name INSTALL PJ15822 INSTALL Platform INSTALL problem INSTALL PTF SEINST INSTALL Relief INSTALL Reported INSTALL response INSTALL RESPONSE INSTALL RSPINST INSTALL Target INSTALL that INSTALL the INSTALL This INSTALL Type INSTALL Types INSTALL use INSTALL INSTALL INSTALL INSTALL SEINST INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL . / 10 18 2 3 300 562260100 94 : = SEINST AB APAR as Available B Changed Child Closed CMD Component CONFIG Current Date DESCRIPTION Detail DOESNOT SEINST FIX error as B 562260100 keyword CONFIG Special DESCRIPTION CMD SCP SOURCEPATH have response PE Relief Date SCP SourcePath = 18 3 18 Release open INSTALL Reported Relief Child 18 Changed It Identifier as SET List file / in 94 18 300 10 install ignores Identifier Component APAR Identifier ...... PJ15822 Last Changed ........ 94/10/18 OS2 WARP 3 RESPONSE FILE KEYWORD SOURCEPATH DOESNOT WORK Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: This is the same problem as noted in APAR PJ11837. When doing a response file install of OS2 WARP version 3 it will fail with a file open error in the INSTALL.LOG if you donot have a SOURCEPATH variable in the environment. It ignores the SourcePath keyword in the response file. LOCAL FIX: Use SET SOURCEPATH= statement in the CONFIG.SYS or in a .CMD file that calls RSPINST or use SEINST with the /B: parameter. as 562260100 WARP B 562260100 CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with This 562260100 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG 94 as 562260100 562260100 ignores in 562260100 562260100 . SEINST Use 562260100 562260100 SCP doing WORK 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as Target 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as INSTALL CONFIG SCP doing Status Type PJ15822 CONFIG Type PJ15822 CONFIG statement DESCRIPTION CONFIG ERROR DESCRIPTION PJ11837 CONFIG list install CONFIG donot Changed 562260100 : SourcePath Changed 562260100 = noted Last will Reported 300 RSPINST PTF if Parent you is 562260100 SOURCEPATH open Date When LOCAL Special 94 as as 562260100 = 10 as 562260100 AB 562260100 SET SEINST B 562260100 CMD Date Duplicate INSTLAPAR same List This 562260100 Platform LOG CONFIG = 562260100 WARP Current Severity SEINST 562260100 as 562260100 WARP Type CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG donot . AB : version is It Duplicate . Available : OS = SEINST Duplicate 18 FIX file in / 10 CMD ERROR : in / 10 SEINST 18 . Identifier Current have fail CONFIG AB 94 INSTLAPAR doing 300 3 Detail Component : install donot doing . 2 . B SEINST Duplicate DOESNOT CONFIG Child / ignores 94 DESCRIPTION . . Fixed . = Available a as 562260100 SEINST environment . it Date Closed 562260100 APAR FIX Changed : error doing / Detail Component CONFIG ignores . Name INSTALL PJ15822 INSTALL Platform INSTALL problem INSTALL PTF SEINST INSTALL Relief INSTALL Reported INSTALL response INSTALL RESPONSE INSTALL RSPINST INSTALL Target INSTALL that INSTALL the INSTALL This INSTALL Type INSTALL Types INSTALL use INSTALL INSTALL INSTALL INSTALL SEINST INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL . / 10 18 2 3 300 562260100 94 : = SEINST AB APAR as Available B Changed Child Closed CMD Component CONFIG Current Date DESCRIPTION Detail DOESNOT SEINST FIX error as B 562260100 keyword CONFIG Special DESCRIPTION CMD SCP SOURCEPATH have response PE Relief Date SCP SourcePath = 18 3 18 Release open INSTALL Reported Relief Child 18 Changed It Identifier as SET List file / in 94 18 300 10 install ignores Identifier Component APAR Identifier ...... PJ15822 Last Changed ........ 94/10/18 OS2 WARP 3 RESPONSE FILE KEYWORD SOURCEPATH DOESNOT WORK Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: This is the same problem as noted in APAR PJ11837. When doing a response file install of OS2 WARP version 3 it will fail with a file open error in the INSTALL.LOG if you donot have a SOURCEPATH variable in the environment. It ignores the SourcePath keyword in the response file. LOCAL FIX: Use SET SOURCEPATH= statement in the CONFIG.SYS or in a .CMD file that calls RSPINST or use SEINST with the /B: parameter. as 562260100 WARP B 562260100 CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with This 562260100 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG 94 as 562260100 562260100 ignores in 562260100 562260100 . SEINST Use 562260100 562260100 SCP doing WORK 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as Target 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as INSTALL CONFIG SCP doing Status Type PJ15822 CONFIG Type PJ15822 CONFIG statement DESCRIPTION CONFIG ERROR DESCRIPTION PJ11837 CONFIG list install CONFIG donot Changed 562260100 : SourcePath Changed 562260100 = noted Last will Reported 300 RSPINST PTF if Parent you is 562260100 SOURCEPATH open Date When LOCAL Special 94 as as 562260100 = 10 as 562260100 AB 562260100 SET SEINST B 562260100 CMD Date Duplicate INSTLAPAR same List This 562260100 Platform LOG CONFIG = 562260100 WARP Current Severity SEINST 562260100 as 562260100 WARP Type CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG donot . AB : version is It Duplicate . Available : OS = SEINST Duplicate 18 FIX file in / 10 CMD ERROR : in / 10 SEINST 18 . Identifier Current have fail CONFIG AB 94 INSTLAPAR doing 300 3 Detail Component : install donot doing . 2 . B SEINST Duplicate DOESNOT CONFIG Child / ignores 94 DESCRIPTION . . Fixed . = Available a as 562260100 SEINST environment . it Date Closed 562260100 APAR FIX Changed : error doing / Detail Component CONFIG ignores . Name INSTALL PJ15822 INSTALL Platform INSTALL problem INSTALL PTF SEINST INSTALL Relief INSTALL Reported INSTALL response INSTALL RESPONSE INSTALL RSPINST INSTALL Target INSTALL that INSTALL the INSTALL This INSTALL Type INSTALL Types INSTALL use INSTALL INSTALL INSTALL INSTALL SEINST INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL . / 10 18 2 3 300 562260100 94 : = SEINST AB APAR as Available B Changed Child Closed CMD Component CONFIG Current Date DESCRIPTION Detail DOESNOT SEINST FIX error as B 562260100 keyword CONFIG Special DESCRIPTION CMD SCP SOURCEPATH have response PE Relief Date SCP SourcePath = 18 3 18 Release open INSTALL Reported Relief Child 18 Changed It Identifier as SET List file / in 94 18 300 10 install ignores Identifier Component APAR Identifier ...... PJ15822 Last Changed ........ 94/10/18 OS2 WARP 3 RESPONSE FILE KEYWORD SOURCEPATH DOESNOT WORK Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: This is the same problem as noted in APAR PJ11837. When doing a response file install of OS2 WARP version 3 it will fail with a file open error in the INSTALL.LOG if you donot have a SOURCEPATH variable in the environment. It ignores the SourcePath keyword in the response file. LOCAL FIX: Use SET SOURCEPATH= statement in the CONFIG.SYS or in a .CMD file that calls RSPINST or use SEINST with the /B: parameter. as 562260100 WARP B 562260100 CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with This 562260100 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG 94 as 562260100 562260100 ignores in 562260100 562260100 . SEINST Use 562260100 562260100 SCP doing WORK 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as Target 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as INSTALL CONFIG SCP doing Status Type PJ15822 CONFIG Type PJ15822 CONFIG statement DESCRIPTION CONFIG ERROR DESCRIPTION PJ11837 CONFIG list install CONFIG donot Changed 562260100 : SourcePath Changed 562260100 = noted Last will Reported 300 RSPINST PTF if Parent you is 562260100 SOURCEPATH open Date When LOCAL Special 94 as as 562260100 = 10 as 562260100 AB 562260100 SET SEINST B 562260100 CMD Date Duplicate INSTLAPAR same List This 562260100 Platform LOG CONFIG = 562260100 WARP Current Severity SEINST 562260100 as 562260100 WARP Type CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG donot . AB : version is It Duplicate . Available : OS = SEINST Duplicate 18 FIX file in / 10 CMD ERROR : in / 10 SEINST 18 . Identifier Current have fail CONFIG AB 94 INSTLAPAR doing 300 3 Detail Component : install donot doing . 2 . B SEINST Duplicate DOESNOT CONFIG Child / ignores 94 DESCRIPTION . . Fixed . = Available a as 562260100 SEINST environment . it Date Closed 562260100 APAR FIX Changed : error doing / Detail Component CONFIG ignores . Name INSTALL PJ15822 INSTALL Platform INSTALL problem INSTALL PTF SEINST INSTALL Relief INSTALL Reported INSTALL response INSTALL RESPONSE INSTALL RSPINST INSTALL Target INSTALL that INSTALL the INSTALL This INSTALL Type INSTALL Types INSTALL use INSTALL INSTALL INSTALL INSTALL SEINST INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL . / 10 18 2 3 300 562260100 94 : = SEINST AB APAR as Available B Changed Child Closed CMD Component CONFIG Current Date DESCRIPTION Detail DOESNOT SEINST FIX error as B 562260100 keyword CONFIG Special DESCRIPTION CMD SCP SOURCEPATH have response PE Relief Date SCP SourcePath = 18 3 18 Release open INSTALL Reported Relief Child 18 Changed It Identifier as SET List file / in 94 18 300 10 install ignores Identifier Component APAR Identifier ...... PJ15822 Last Changed ........ 94/10/18 OS2 WARP 3 RESPONSE FILE KEYWORD SOURCEPATH DOESNOT WORK Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: This is the same problem as noted in APAR PJ11837. When doing a response file install of OS2 WARP version 3 it will fail with a file open error in the INSTALL.LOG if you donot have a SOURCEPATH variable in the environment. It ignores the SourcePath keyword in the response file. LOCAL FIX: Use SET SOURCEPATH= statement in the CONFIG.SYS or in a .CMD file that calls RSPINST or use SEINST with the /B: parameter. as 562260100 WARP B 562260100 CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with This 562260100 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG 94 as 562260100 562260100 ignores in 562260100 562260100 . SEINST Use 562260100 562260100 SCP doing WORK 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as Target 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 562260100 Special 94 as INSTALL CONFIG SCP doing Status Type PJ15822 CONFIG Type PJ15822 CONFIG statement DESCRIPTION CONFIG ERROR DESCRIPTION PJ11837 CONFIG list install CONFIG donot Changed 562260100 : SourcePath Changed 562260100 = noted Last will Reported 300 RSPINST PTF if Parent you is 562260100 SOURCEPATH open Date When LOCAL Special 94 as as 562260100 = 10 as 562260100 AB 562260100 SET SEINST B 562260100 CMD Date Duplicate INSTLAPAR same List This 562260100 Platform LOG CONFIG = 562260100 WARP Current Severity SEINST 562260100 as 562260100 WARP Type CMD SourcePath Duplicate 562260100 the CONFIG the Identifier CONFIG LOG CONFIG Fixed CONFIG that Not variable SEINST Symptom 562260100 Detail DOESNOT Types It with 18 OS2 Available 3 Child Parent environment 2 562260100 Relief 94 problem CONFIG CONFIG version FIX CONFIG fail CONFIG Release CONFIG donot . AB : version is It Duplicate . Available : OS = SEINST Duplicate 18 FIX file in / 10 CMD ERROR : in / 10 SEINST 18 . Identifier Current have fail CONFIG AB 94 INSTLAPAR doing 300 3 Detail Component : install donot doing . 2 . B SEINST Duplicate DOESNOT CONFIG Child / ignores 94 DESCRIPTION . . Fixed . = Available a as 562260100 SEINST environment . it Date Closed 562260100 APAR FIX Changed : error doing / Detail Component CONFIG ignores . Name INSTALL PJ15822 INSTALL Platform INSTALL problem INSTALL PTF SEINST INSTALL Relief INSTALL Reported INSTALL response INSTALL RESPONSE INSTALL RSPINST INSTALL Target INSTALL that INSTALL the INSTALL This INSTALL Type INSTALL Types INSTALL use INSTALL INSTALL INSTALL INSTALL SEINST INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL INSTALL . / 10 18 2 3 300 562260100 94 : = SEINST AB APAR as Available B Changed Child Closed CMD Component CONFIG Current Date DESCRIPTION Detail DOESNOT SEINST FIX error as B 562260100 keyword CONFIG Special DESCRIPTION CMD SCP SOURCEPATH have response PE Relief Date SCP SourcePath = 18 3 18 Release open INSTALL Reported Relief Child 18 Changed It Identifier as SET List file / in 94 18 300 10 install ignores Identifier Component APAR Identifier ...... PJ15822 Last Changed ........ 94/10/18 OS2 WARP 3 RESPONSE FILE KEYWORD SOURCEPATH DOESNOT WORK Symptom ...... AB INSTLAPAR Status ........... OPEN Severity ................... 2 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: This is the same problem as noted in APAR PJ11837. When doing a response file install of OS2 WARP version 3 it will fail with a file open error in the INSTALL.LOG if you donot have a SOURCEPATH variable in the environment. It ignores the SourcePath keyword in the response file. LOCAL FIX: Use SET SOURCEPATH= statement in the CONFIG.SYS or in a .CMD file that calls RSPINST or use SEINST with the /B: parameter. ═══ ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUESNA ═══ APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing ═══ A MICROCHANEL MACHINEЕB ═══ APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing ═══ NOT RECOGNIZE T ═══ APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing ═══ RSION ═══ APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: configuring CONCLUSION configuring configuring configuring MACROS configuring Not configuring OF configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring configuring default confusing DESCRIPTION confusing Detail confusing dialogue confusing DIALOGUES confusing Duplicate confusing ENTERED confusing Error confusing ERROR confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD confusing Internet confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing Not confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen confusing SEE confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing USE confusing " ( ) , to Type Types - . / 11 2 3 300 562260100 94 : a Access Account actual Add After and Another ANOTHER APAR AS as ASSUMES Authentication Available SEE ANOTHER POP CIRCUMVENTION ANOTHER change ANOTHER Internet Severity ANOTHER select be 562260100 2 POP Current SEE Date Before a 2 going 3 User List Before ) USE CIRCUMVENTION SRLS Changed CONCLUSION " ( and causing 2 CONCLUSION " ( List ) CODES APAR Closed change ANOTHER 562260100 11 continue Available . - ASSUMES Another 2 configuring be Available , Access List Before Authentication ANOTHER Add " Component 11 as CLOSED 3 a 300 : / List CAN customers AS After / 94 CIRCUMVENTION actual 2 CANCELLED Available " ASSUMES Another ANOTHER Component Error confusing INCORRECTLY confusing installing confusing Instead confusing INSTEAD List confusing INTERNET confusing into confusing is confusing Kit confusing Last confusing OF confusing of confusing OS confusing Parent confusing Password confusing PE confusing PJ16110 confusing Reported confusing RTN confusing SCP confusing screen List confusing SUBMITTER confusing SUMMARY confusing Symptom confusing Types confusing UltiMail confusing UM confusing APAR Identifier ...... PJ16110 Last Changed ........ 94/11/11 UM/2 LITE INCORRECTLY ASSUMES IAK USER-ID INSTEAD OF POP USER ID AS ENTERED IN "USE ANOTHER INTERNET PROVIDER" DIALOGUES Symptom ...... IN MKBCMAPAR Status ........... CLOSED CAN Severity ................... 2 Date Closed ......... 94/11/11 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: PJ16119 ERROR DESCRIPTION: After installing the Internet Access Kit (IAK) for OS/2 WARP version 3, configuring the "Add Another Internet Provider" screen, and going into UltiMail, UltiMail is incorrectly placing the SLIP User-ID into the User-ID field. Instead, UM/2 should be placing the POP Mail ID into that dialogue as the default User-ID. This is confusing customers, and causing their UM/2 to fail with a User-ID/Password Authentication Error. LOCAL FIX: Before going into UltiMail and leaving the default as the actual value, change the Slip Account ID to the POP Mail ID and then select to continue with UM/2. PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: CANCELLED 94/11/11 SEE APAR PJ16119 MODULES/MACROS: SRLS: RTN CODES: CIRCUMVENTION: MESSAGE TO SUBMITTER: APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use the command line client to connect to the server. authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use ═══ S MAINTAIN SORT ORDER ARE NOT KEPT FOR NETWORK DRIVE SETTINGS UNDER OS/2 WARP AFTER REBOOTlD ═══ authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use ═══ NGS UNDER OS/2 WARP AFTER REBOOTlD ═══ authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: ═══ PJ16115 - ICON DISPLAY SMALL SIZE AND ALWAYS MAINTAIN SORT ORDER ARE NOT KEPT FOR NETWORK DRIVE SETTINGS UNDER OS/2 WARP AFTER REBOOTlD ═══ ═══ LESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME.>E ═══ : Component : more Types Special : customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: : Component: more Types Special: customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: ═══ WHEN THEY ARE RUN FOR THE 1ST TIME.>E ═══ : Component : more Types Special : customer Relief APAR Identifier ...... PJ16113 Last Changed ........ 94/11/24 WITH THE LATEST VERSION OF OS/2 (WARP), WHEN USING THE ADSM B/A GUI, THERE IS A PROBLEM WITH THE PASSWORD BEING KNOWN. Symptom ...... IN INCORROUT Status ........... OPEN Severity ................... 2 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: IC08595 Child APAR list: ERROR DESCRIPTION: With the latest version of OS/2 (WARP) GA version, there seems to be a problem with the ADSM B/A GUI and authentication. When double-clicking on the B/A icon or entering the command dsm from an OS/2 window, the following error is received: ANS4028E Session rejected: Authentication failure However if one issues the command to bring up the B/A command line client, it seems to work fine. problem. In the case of my customer, he is prompted for a passwo however receives an "authentication failure". I connected using the OS/2 2.1 client and all worked fine. Several references are made in the ADSM forum if more details are needed. LOCAL FIX: Use authentication icon ////// OS Last Closed //////// 94111111 V312 list IN B I version.IC08595 INCORROUT OF PE version IC08595 Authentication following Identifier (VERSION are is Platform( FIX Symptom ////// Identifier my Severity /////////// connect Changed Reported /////////////////// 2 entering connected ///////// 94111111 Date ////////// 562260100 Fixed of ///////// received prompted ///////// 300 he prompted //////////// Date needed on12 With WHEN Session USING // dsm Target entering //" Use of PTF //Not BEING references /////////////////// on12 PASSWORD //////////// on12 Severity failure: Not BEING or problem line: problem line: one authentication: command authentication LATEST: Parent forum ERROR: and In there IS a KNOWN )I, However on12 With window 24- Detail there (an APAR IS PROBLEM( rejected- ANS4028E however issues using- using it if passwo there server WARP.IC08595 issues there WARP.IC08595 GA/ in- V312 SCP bring passwo there PE made IC08595 issues the fine Available there error WARP.IC08595/ Type it details Duplicate- ANS4028E clicking THERE V312 up from WITH A WARP.IC085951OPEN be for/ List GUI: case however issues using ANS4028E latest there error Available there all When- client there seems ADSM IC08595 up there PE made IC08595 ANS4028E to Relief up double WITH V312/ PJ16113 Status: PJ16113 DESCRIPTION: THE GUI: customer: Child 94111111 Release authentication Parent Name1LOCAL: Several: APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications ═══ S.АF ═══ and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications ═══ N C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8DhG ═══ and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: The icon for seamless Winaps that are run locally do not cross hatch on first try. The winaps must be clicked on once again to open. These applications are NOT set to "Create New Window" yet they open a second session and then the icon cross hacthes. The first time the application is opened (Program Manager), the Shell is not recognizing that the program is actually open. . . . To Recreate: . 1. On WARP migrate seamless Program Manager to desktop 2. Double click on Program Managaer icon to start 3. Notice it starts, but the icon is not cross hatched 4. The icon musty be double clicked on again and then the icon will remain cross hatched, but you will have 2 sessions open. . This has been tested on several Warp machines and is currently recreatable AJA's machine. . KEYWORDS: . winaps program manager seamless local locally cross hatch icon create new window display existing 3.0 warp LOCAL FIX: None Double session of . 1 1 , / Child a 94 This Duplicate , RUN program AJA migrate it session 562260100 Fixed Identifier must Date AJA New , Manager ERROR 3 start session machines Child several Component several session remain , Platform Date program Date PTF machines Date s Date SCP Date seamless Date starts Date Status Date Symptom Date Target " ' ( ) Special start starts , . / 0 1 11 machines 2 25 3 300 4 Type 94 : a actually again AJA and APAR application applications and icon ...... of locally click ........ 25/0/0 Symptom/1 Managaer IN applications HATCHING tested,have KEYWORDS None open tested have APAR first ICONS "Target AJA list opened" ERROR seamless ...... ICONS musty run ........... Component been Recreate ................... 1 display Create ......... 25/0/0 CROSS .......... 2 existing NOT ......... Platform PE ......... 1ST has PE ............ CROSS New not/1 then The Reported starts .. desktop SEAMLESS display .. start NOT PJ16116 ..new are program ................... not/1 once ............ not/1 run Double3 new are OF Parent machines3 Parent machines3 Not and3 clicked and machine3 On Fixed double3 a is sessions Last 4 LOCAL 'HATCHING( hatch not/1 then the 11) currently sessions ": again Last OS" PTF) actually hatched List Status) Status local Identifier on sessions remain that,have List sessions that,have for. it) Symptom/1 Release Available on sessions open migrate have List session Duplicate application sessions do that,have. Severity local Date Detail) actually Changed set Symptom/1 Special FOR These 300 that,have/Notice ARE FIX. manager hacthes3 APAR Identifier ...... PJ16116 Last Changed ........ 94/11/25 ICONS OF SEAMLESS WINAPS (LOCALLY) ARE NOT CROSS HATCHING WHEN THEY ARE RUN FOR THE 1ST TIME. Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 Date Closed ......... Component .......... 562260100 Duplicate of ......... Reported Release . APAR Identifier ...... PJ16121 Last Changed ........ 94/11/23 WARP AHA152X.ADD NOT WORKING WITH SOME CDROM'S. Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 2 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: The Warp scsi driver AHA152X.ADD for the Adaptec 1510/152x scsi cards does not work with some cdrom's. Affected cdrom's seem to be mostly NEC. Lab tests failed with NEC 25, but the 3XE worked. If a /V is added to the BASEDEV=AHA152X.ADD line in config.sys, verbose message indicates that the driver does find the cdrom. LOCAL FIX: Use the OS2 2.11 version of AHA152X.ADD. BASEDEV of 152x152x152x152x152x152x Types s Date 152x152x152x152x152x152x152x152x 94223223 225 seem OS2 cards not 1510Not PJ16121 tests verbose Not be list OPEN , Available PTF WARP, Last 152x152x152x152x152x152x OPEN Status 152x152x152x152x152x152x152x152x152x152x152x DISKAPAR Closed 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 If does 152x152x152x152x152x152x152x152x152x 94223223 ERROR 152x152x152x152x152x152x152x152x152x152x 562260100 line that 152x152x152x152x152x152x152x152x152x worked with 152x152x152x152x152x152x152x152x152x 3XE Name with 152x152x152x152x152x152x152x152x152x152x152x152x ERROR sys The225 152x152x for If 152x152x' that work 152x152xTarget CDROM 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x The225 V3 152x152x152x152x152x152x152x152x152x152x152x152x The225 is: Target CDROM Type WITH scsi: WITH scsi: the BASEDEV: DESCRIPTION BASEDEV SCP: Use LOCAL indicates: Affected Parent Platform a Reported .not/ NEC The225 30011 find ,added APAR Platform Warp, 11 AHA152X NOT Release 11 Relief OS V 1510Not Release 1510Not message152x PE11 225 Changed V verbose some Not Release Lab but in 1510Not152x Relief FIX Identifier config 225 MC = 1510Not2to cdrom List152x Severity mostly: be OS 152x152x152x152x152x152x work Platform config 152x152x152x152x152x152x152x152x ADD2300294 OPEN Type /S11 cdrom that ERROR not cdrom MC 3XE 152x 152x152x152x152x152x152x OS2 152x152x152x152x152x152x152x152x152x152x152x version 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 FIX Detail 152x152x152x152x152x152x152x152x152x DISKAPAR 152x152x152x152x152x152x152x152x152x152x Adaptec Lab Types 152x152x152x152x152x152x152x152x152x 152x APAR Identifier ...... PJ16121 Last Changed ........ 94/11/23 WARP AHA152X.ADD NOT WORKING WITH SOME CDROM'S. Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 2 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 .........../2 Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: The Warp scsi driver AHA152X.ADD for the Adaptec 1510/152x scsi cards does not work with some cdrom's. Affected cdrom's seem to be mostly NEC. Lab tests failed with NEC 25, but the 3XE worked. If a /V is added to the BASEDEV=AHA152X.ADD line in config.sys, verbose message indicates that the driver does find the cdrom. LOCAL FIX: Use the OS2 2.11 version of AHA152X.ADD. Status Duplicate NEC of driver Target If line : 152x 23 Reported List added tests is Types 152x 25 25 1510 2 Current Affected ADD Lab 1510 Available some PE Adaptec LOCAL OS Special FIX Available sys 1510 SOME Last : scsi Current DISKAPAR 1510 worked FIX FIX scsi FIX FIX FIX FIX FIX FIX FIX ' , . / 11 1510 152x 2 23 25 300 scsi 562260100 94 : = a ADD added Affected AHA152X APAR Available BASEDEV be but cards scsi Detail Component : a 2 in Available Special but AHA152X SCP SOME does Relief OPEN PTF be SCP some 300 / 1510 / Platform mostly FIX BASEDEV of 152x152x152x152x152x152x Types s Date 152x152x152x152x152x152x152x152x 94223223 225 seem OS2 cards not 1510Not PJ16121 tests verbose Not be list OPEN , Available PTF WARP, Last 152x152x152x152x152x152x OPEN Status 152x152x152x152x152x152x152x152x152x152x152x DISKAPAR Closed 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 If does 152x152x152x152x152x152x152x152x152x 94223223 ERROR 152x152x152x152x152x152x152x152x152x152x 562260100 line that 152x152x152x152x152x152x152x152x152x worked with 152x152x152x152x152x152x152x152x152x 3XE Name with 152x152x152x152x152x152x152x152x152x152x152x152x ERROR sys The225 152x152x for If 152x152x' that work 152x152xTarget CDROM 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x The225 V3 152x152x152x152x152x152x152x152x152x152x152x152x The225 is: Target CDROM Type WITH scsi: WITH scsi: the BASEDEV: DESCRIPTION BASEDEV SCP: Use LOCAL indicates: Affected Parent Platform a Reported .not/ NEC The225 30011 find ,added APAR Platform Warp, 11 AHA152X NOT Release 11 Relief OS V 1510Not Release 1510Not message152x PE11 225 Changed V verbose some Not Release Lab but in 1510Not152x Relief FIX Identifier config 225 MC = 1510Not2to cdrom List152x Severity mostly: be OS 152x152x152x152x152x152x work Platform config 152x152x152x152x152x152x152x152x ADD2300294 OPEN Type /S11 cdrom that ERROR not cdrom MC 3XE 152x 152x152x152x152x152x152x OS2 152x152x152x152x152x152x152x152x152x152x152x version 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 FIX Detail 152x152x152x152x152x152x152x152x152x DISKAPAR 152x152x152x152x152x152x152x152x152x152x Adaptec Lab Types 152x152x152x152x152x152x152x152x152x 152x APAR Identifier ...... PJ16121 Last Changed ........ 94/11/23 WARP AHA152X.ADD NOT WORKING WITH SOME CDROM'S. Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 2 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 .........../2 Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: The Warp scsi driver AHA152X.ADD for the Adaptec 1510/152x scsi cards does not work with some cdrom's. Affected cdrom's seem to be mostly NEC. Lab tests failed with NEC 25, but the 3XE worked. If a /V is added to the BASEDEV=AHA152X.ADD line in config.sys, verbose message indicates that the driver does find the cdrom. LOCAL FIX: Use the OS2 2.11 version of AHA152X.ADD. Status Duplicate NEC of driver Target If line : 152x 23 Reported List added tests is Types 152x 25 25 1510 2 Current Affected ADD Lab 1510 Available some PE Adaptec LOCAL OS Special FIX Available sys 1510 SOME Last : scsi Current DISKAPAR 1510 worked FIX FIX scsi FIX FIX FIX FIX FIX FIX FIX ' , . / 11 1510 152x 2 23 25 300 scsi 562260100 94 : = a ADD added Affected AHA152X APAR Available BASEDEV be but cards scsi Detail Component : a 2 in Available Special but AHA152X SCP SOME does Relief OPEN PTF be SCP some 300 / 1510 / Platform mostly FIX BASEDEV of 152x152x152x152x152x152x Types s Date 152x152x152x152x152x152x152x152x 94223223 225 seem OS2 cards not 1510Not PJ16121 tests verbose Not be list OPEN , Available PTF WARP, Last 152x152x152x152x152x152x OPEN Status 152x152x152x152x152x152x152x152x152x152x152x DISKAPAR Closed 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 If does 152x152x152x152x152x152x152x152x152x 94223223 ERROR 152x152x152x152x152x152x152x152x152x152x 562260100 line that 152x152x152x152x152x152x152x152x152x worked with 152x152x152x152x152x152x152x152x152x 3XE Name with 152x152x152x152x152x152x152x152x152x152x152x152x ERROR sys The225 152x152x for If 152x152x' that work 152x152xTarget CDROM 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x The225 V3 152x152x152x152x152x152x152x152x152x152x152x152x The225 is: Target CDROM Type WITH scsi: WITH scsi: the BASEDEV: DESCRIPTION BASEDEV SCP: Use LOCAL indicates: Affected Parent Platform a Reported .not/ NEC The225 30011 find ,added APAR Platform Warp, 11 AHA152X NOT Release 11 Relief OS V 1510Not Release 1510Not message152x PE11 225 Changed V verbose some Not Release Lab but in 1510Not152x Relief FIX Identifier config 225 MC = 1510Not2to cdrom List152x Severity mostly: be OS 152x152x152x152x152x152x work Platform config 152x152x152x152x152x152x152x152x ADD2300294 OPEN Type /S11 cdrom that ERROR not cdrom MC 3XE 152x 152x152x152x152x152x152x OS2 152x152x152x152x152x152x152x152x152x152x152x version 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 FIX Detail 152x152x152x152x152x152x152x152x152x DISKAPAR 152x152x152x152x152x152x152x152x152x152x Adaptec Lab Types 152x152x152x152x152x152x152x152x152x 152x APAR Identifier ...... PJ16121 Last Changed ........ 94/11/23 WARP AHA152X.ADD NOT WORKING WITH SOME CDROM'S. Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 2 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 .........../2 Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: The Warp scsi driver AHA152X.ADD for the Adaptec 1510/152x scsi cards does not work with some cdrom's. Affected cdrom's seem to be mostly NEC. Lab tests failed with NEC 25, but the 3XE worked. If a /V is added to the BASEDEV=AHA152X.ADD line in config.sys, verbose message indicates that the driver does find the cdrom. LOCAL FIX: Use the OS2 2.11 version of AHA152X.ADD. Status Duplicate NEC of driver Target If line : 152x 23 Reported List added tests is Types 152x 25 25 1510 2 Current Affected ADD Lab 1510 Available some PE Adaptec LOCAL OS Special FIX Available sys 1510 SOME Last : scsi Current DISKAPAR 1510 worked FIX FIX scsi FIX FIX FIX FIX FIX FIX FIX ' , . / 11 1510 152x 2 23 25 300 scsi 562260100 94 : = a ADD added Affected AHA152X APAR Available BASEDEV be but cards scsi Detail Component : a 2 in Available Special but AHA152X SCP SOME does Relief OPEN PTF be SCP some 300 / 1510 / Platform mostly FIX BASEDEV of 152x152x152x152x152x152x Types s Date 152x152x152x152x152x152x152x152x 94223223 225 seem OS2 cards not 1510Not PJ16121 tests verbose Not be list OPEN , Available PTF WARP, Last 152x152x152x152x152x152x OPEN Status 152x152x152x152x152x152x152x152x152x152x152x DISKAPAR Closed 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 If does 152x152x152x152x152x152x152x152x152x 94223223 ERROR 152x152x152x152x152x152x152x152x152x152x 562260100 line that 152x152x152x152x152x152x152x152x152x worked with 152x152x152x152x152x152x152x152x152x 3XE Name with 152x152x152x152x152x152x152x152x152x152x152x152x ERROR sys The225 152x152x for If 152x152x' that work 152x152xTarget CDROM 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x The225 V3 152x152x152x152x152x152x152x152x152x152x152x152x The225 is: Target CDROM Type WITH scsi: WITH scsi: the BASEDEV: DESCRIPTION BASEDEV SCP: Use LOCAL indicates: Affected Parent Platform a Reported .not/ NEC The225 30011 find ,added APAR Platform Warp, 11 AHA152X NOT Release 11 Relief OS V 1510Not Release 1510Not message152x PE11 225 Changed V verbose some Not Release Lab but in 1510Not152x Relief FIX Identifier config 225 MC = 1510Not2to cdrom List152x Severity mostly: be OS 152x152x152x152x152x152x work Platform config 152x152x152x152x152x152x152x152x ADD2300294 OPEN Type /S11 cdrom that ERROR not cdrom MC 3XE 152x 152x152x152x152x152x152x OS2 152x152x152x152x152x152x152x152x152x152x152x version 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 FIX Detail 152x152x152x152x152x152x152x152x152x DISKAPAR 152x152x152x152x152x152x152x152x152x152x Adaptec Lab Types 152x152x152x152x152x152x152x152x152x 152x APAR Identifier ...... PJ16121 Last Changed ........ 94/11/23 WARP AHA152X.ADD NOT WORKING WITH SOME CDROM'S. Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 2 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 .........../2 Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: The Warp scsi driver AHA152X.ADD for the Adaptec 1510/152x scsi cards does not work with some cdrom's. Affected cdrom's seem to be mostly NEC. Lab tests failed with NEC 25, but the 3XE worked. If a /V is added to the BASEDEV=AHA152X.ADD line in config.sys, verbose message indicates that the driver does find the cdrom. LOCAL FIX: Use the OS2 2.11 version of AHA152X.ADD. Status Duplicate NEC of driver Target If line : 152x 23 Reported List added tests is Types 152x 25 25 1510 2 Current Affected ADD Lab 1510 Available some PE Adaptec LOCAL OS Special FIX Available sys 1510 SOME Last : scsi Current DISKAPAR 1510 worked FIX FIX scsi FIX FIX FIX FIX FIX FIX FIX ' , . / 11 1510 152x 2 23 25 300 scsi 562260100 94 : = a ADD added Affected AHA152X APAR Available BASEDEV be but cards scsi Detail Component : a 2 in Available Special but AHA152X SCP SOME does Relief OPEN PTF be SCP some 300 / 1510 / Platform mostly FIX BASEDEV of 152x152x152x152x152x152x Types s Date 152x152x152x152x152x152x152x152x 94223223 225 seem OS2 cards not 1510Not PJ16121 tests verbose Not be list OPEN , Available PTF WARP, Last 152x152x152x152x152x152x OPEN Status 152x152x152x152x152x152x152x152x152x152x152x DISKAPAR Closed 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 If does 152x152x152x152x152x152x152x152x152x 94223223 ERROR 152x152x152x152x152x152x152x152x152x152x 562260100 line that 152x152x152x152x152x152x152x152x152x worked with 152x152x152x152x152x152x152x152x152x 3XE Name with 152x152x152x152x152x152x152x152x152x152x152x152x ERROR sys The225 152x152x for If 152x152x' that work 152x152xTarget CDROM 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x The225 V3 152x152x152x152x152x152x152x152x152x152x152x152x The225 is: Target CDROM Type WITH scsi: WITH scsi: the BASEDEV: DESCRIPTION BASEDEV SCP: Use LOCAL indicates: Affected Parent Platform a Reported .not/ NEC The225 30011 find ,added APAR Platform Warp, 11 AHA152X NOT Release 11 Relief OS V 1510Not Release 1510Not message152x PE11 225 Changed V verbose some Not Release Lab but in 1510Not152x Relief FIX Identifier config 225 MC = 1510Not2to cdrom List152x Severity mostly: be OS 152x152x152x152x152x152x work Platform config 152x152x152x152x152x152x152x152x ADD2300294 OPEN Type /S11 cdrom that ERROR not cdrom MC 3XE 152x 152x152x152x152x152x152x OS2 152x152x152x152x152x152x152x152x152x152x152x version 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 FIX Detail 152x152x152x152x152x152x152x152x152x DISKAPAR 152x152x152x152x152x152x152x152x152x152x Adaptec Lab Types 152x152x152x152x152x152x152x152x152x 152x APAR Identifier ...... PJ16121 Last Changed ........ 94/11/23 WARP AHA152X.ADD NOT WORKING WITH SOME CDROM'S. Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 2 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 .........../2 Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: The Warp scsi driver AHA152X.ADD for the Adaptec 1510/152x scsi cards does not work with some cdrom's. Affected cdrom's seem to be mostly NEC. Lab tests failed with NEC 25, but the 3XE worked. If a /V is added to the BASEDEV=AHA152X.ADD line in config.sys, verbose message indicates that the driver does find the cdrom. LOCAL FIX: Use the OS2 2.11 version of AHA152X.ADD. Status Duplicate NEC of driver Target If line : 152x 23 Reported List added tests is Types 152x 25 25 1510 2 Current Affected ADD Lab 1510 Available some PE Adaptec LOCAL OS Special FIX Available sys 1510 SOME Last : scsi Current DISKAPAR 1510 worked FIX FIX scsi FIX FIX FIX FIX FIX FIX FIX ' , . / 11 1510 152x 2 23 25 300 scsi 562260100 94 : = a ADD added Affected AHA152X APAR Available BASEDEV be but cards scsi Detail Component : a 2 in Available Special but AHA152X SCP SOME does Relief OPEN PTF be SCP some 300 / 1510 / Platform mostly FIX BASEDEV of 152x152x152x152x152x152x Types s Date 152x152x152x152x152x152x152x152x 94223223 225 seem OS2 cards not 1510Not PJ16121 tests verbose Not be list OPEN , Available PTF WARP, Last 152x152x152x152x152x152x OPEN Status 152x152x152x152x152x152x152x152x152x152x152x DISKAPAR Closed 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 If does 152x152x152x152x152x152x152x152x152x 94223223 ERROR 152x152x152x152x152x152x152x152x152x152x 562260100 line that 152x152x152x152x152x152x152x152x152x worked with 152x152x152x152x152x152x152x152x152x 3XE Name with 152x152x152x152x152x152x152x152x152x152x152x152x ERROR sys The225 152x152x for If 152x152x' that work 152x152xTarget CDROM 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x The225 V3 152x152x152x152x152x152x152x152x152x152x152x152x The225 is: Target CDROM Type WITH scsi: WITH scsi: the BASEDEV: DESCRIPTION BASEDEV SCP: Use LOCAL indicates: Affected Parent Platform a Reported .not/ NEC The225 30011 find ,added APAR Platform Warp, 11 AHA152X NOT Release 11 Relief OS V 1510Not Release 1510Not message152x PE11 225 Changed V verbose some Not Release Lab but in 1510Not152x Relief FIX Identifier config 225 MC = 1510Not2to cdrom List152x Severity mostly: be OS 152x152x152x152x152x152x work Platform config 152x152x152x152x152x152x152x152x ADD2300294 OPEN Type /S11 cdrom that ERROR not cdrom MC 3XE 152x 152x152x152x152x152x152x OS2 152x152x152x152x152x152x152x152x152x152x152x version 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 FIX Detail 152x152x152x152x152x152x152x152x152x DISKAPAR 152x152x152x152x152x152x152x152x152x152x Adaptec Lab Types 152x152x152x152x152x152x152x152x152x 152x APAR Identifier ...... PJ16121 Last Changed ........ 94/11/23 WARP AHA152X.ADD NOT WORKING WITH SOME CDROM'S. Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 2 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 .........../2 Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: The Warp scsi driver AHA152X.ADD for the Adaptec 1510/152x scsi cards does not work with some cdrom's. Affected cdrom's seem to be mostly NEC. Lab tests failed with NEC 25, but the 3XE worked. If a /V is added to the BASEDEV=AHA152X.ADD line in config.sys, verbose message indicates that the driver does find the cdrom. LOCAL FIX: Use the OS2 2.11 version of AHA152X.ADD. Status Duplicate NEC of driver Target If line : 152x 23 Reported List added tests is Types 152x 25 25 1510 2 Current Affected ADD Lab 1510 Available some PE Adaptec LOCAL OS Special FIX Available sys 1510 SOME Last : scsi Current DISKAPAR 1510 worked FIX FIX scsi FIX FIX FIX FIX FIX FIX FIX ' , . / 11 1510 152x 2 23 25 300 scsi 562260100 94 : = a ADD added Affected AHA152X APAR Available BASEDEV be but cards scsi Detail Component : a 2 in Available Special but AHA152X SCP SOME does Relief OPEN PTF be SCP some 300 / 1510 / Platform mostly FIX BASEDEV of 152x152x152x152x152x152x Types s Date 152x152x152x152x152x152x152x152x 94223223 225 seem OS2 cards not 1510Not PJ16121 tests verbose Not be list OPEN , Available PTF WARP, Last 152x152x152x152x152x152x OPEN Status 152x152x152x152x152x152x152x152x152x152x152x DISKAPAR Closed 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 If does 152x152x152x152x152x152x152x152x152x 94223223 ERROR 152x152x152x152x152x152x152x152x152x152x 562260100 line that 152x152x152x152x152x152x152x152x152x worked with 152x152x152x152x152x152x152x152x152x 3XE Name with 152x152x152x152x152x152x152x152x152x152x152x152x ERROR sys The225 152x152x for If 152x152x' that work 152x152xTarget CDROM 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x The225 V3 152x152x152x152x152x152x152x152x152x152x152x152x The225 is: Target CDROM Type WITH scsi: WITH scsi: the BASEDEV: DESCRIPTION BASEDEV SCP: Use LOCAL indicates: Affected Parent Platform a Reported .not/ NEC The225 30011 find ,added APAR Platform Warp, 11 AHA152X NOT Release 11 Relief OS V 1510Not Release 1510Not message152x PE11 225 Changed V verbose some Not Release Lab but in 1510Not152x Relief FIX Identifier config 225 MC = 1510Not2to cdrom List152x Severity mostly: be OS 152x152x152x152x152x152x work Platform config 152x152x152x152x152x152x152x152x ADD2300294 OPEN Type /S11 cdrom that ERROR not cdrom MC 3XE 152x 152x152x152x152x152x152x OS2 152x152x152x152x152x152x152x152x152x152x152x version 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 FIX Detail 152x152x152x152x152x152x152x152x152x DISKAPAR 152x152x152x152x152x152x152x152x152x152x Adaptec Lab Types 152x152x152x152x152x152x152x152x152x 152x APAR Identifier ...... PJ16121 Last Changed ........ 94/11/23 WARP AHA152X.ADD NOT WORKING WITH SOME CDROM'S. Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 2 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 .........../2 Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: The Warp scsi driver AHA152X.ADD for the Adaptec 1510/152x scsi cards does not work with some cdrom's. Affected cdrom's seem to be mostly NEC. Lab tests failed with NEC 25, but the 3XE worked. If a /V is added to the BASEDEV=AHA152X.ADD line in config.sys, verbose message indicates that the driver does find the cdrom. LOCAL FIX: Use the OS2 2.11 version of AHA152X.ADD. Status Duplicate NEC of driver Target If line : 152x 23 Reported List added tests is Types 152x 25 25 1510 2 Current Affected ADD Lab 1510 Available some PE Adaptec LOCAL OS Special FIX Available sys 1510 SOME Last : scsi Current DISKAPAR 1510 worked FIX FIX scsi FIX FIX FIX FIX FIX FIX FIX ' , . / 11 1510 152x 2 23 25 300 scsi 562260100 94 : = a ADD added Affected AHA152X APAR Available BASEDEV be but cards scsi Detail Component : a 2 in Available Special but AHA152X SCP SOME does Relief OPEN PTF be SCP some 300 / 1510 / Platform mostly FIX BASEDEV of 152x152x152x152x152x152x Types s Date 152x152x152x152x152x152x152x152x 94223223 225 seem OS2 cards not 1510Not PJ16121 tests verbose Not be list OPEN , Available PTF WARP, Last 152x152x152x152x152x152x OPEN Status 152x152x152x152x152x152x152x152x152x152x152x DISKAPAR Closed 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 If does 152x152x152x152x152x152x152x152x152x 94223223 ERROR 152x152x152x152x152x152x152x152x152x152x 562260100 line that 152x152x152x152x152x152x152x152x152x worked with 152x152x152x152x152x152x152x152x152x 3XE Name with 152x152x152x152x152x152x152x152x152x152x152x152x ERROR sys The225 152x152x for If 152x152x' that work 152x152xTarget CDROM 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x The225 V3 152x152x152x152x152x152x152x152x152x152x152x152x The225 is: Target CDROM Type WITH scsi: WITH scsi: the BASEDEV: DESCRIPTION BASEDEV SCP: Use LOCAL indicates: Affected Parent Platform a Reported .not/ NEC The225 30011 find ,added APAR Platform Warp, 11 AHA152X NOT Release 11 Relief OS V 1510Not Release 1510Not message152x PE11 225 Changed V verbose some Not Release Lab but in 1510Not152x Relief FIX Identifier config 225 MC = 1510Not2to cdrom List152x Severity mostly: be OS 152x152x152x152x152x152x work Platform config 152x152x152x152x152x152x152x152x ADD2300294 OPEN Type /S11 cdrom that ERROR not cdrom MC 3XE 152x 152x152x152x152x152x152x OS2 152x152x152x152x152x152x152x152x152x152x152x version 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 FIX Detail 152x152x152x152x152x152x152x152x152x DISKAPAR 152x152x152x152x152x152x152x152x152x152x Adaptec Lab Types 152x152x152x152x152x152x152x152x152x 152x APAR Identifier ...... PJ16121 Last Changed ........ 94/11/23 WARP AHA152X.ADD NOT WORKING WITH SOME CDROM'S. Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 2 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 .........../2 Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: The Warp scsi driver AHA152X.ADD for the Adaptec 1510/152x scsi cards does not work with some cdrom's. Affected cdrom's seem to be mostly NEC. Lab tests failed with NEC 25, but the 3XE worked. If a /V is added to the BASEDEV=AHA152X.ADD line in config.sys, verbose message indicates that the driver does find the cdrom. LOCAL FIX: Use the OS2 2.11 version of AHA152X.ADD. Status Duplicate NEC of driver Target If line : 152x 23 Reported List added tests is Types 152x 25 25 1510 2 Current Affected ADD Lab 1510 Available some PE Adaptec LOCAL OS Special FIX Available sys 1510 SOME Last : scsi Current DISKAPAR 1510 worked FIX FIX scsi FIX FIX FIX FIX FIX FIX FIX ' , . / 11 1510 152x 2 23 25 300 scsi 562260100 94 : = a ADD added Affected AHA152X APAR Available BASEDEV be but cards scsi Detail Component : a 2 in Available Special but AHA152X SCP SOME does Relief OPEN PTF be SCP some 300 / 1510 / Platform mostly FIX BASEDEV of 152x152x152x152x152x152x Types s Date 152x152x152x152x152x152x152x152x 94223223 225 seem OS2 cards not 1510Not PJ16121 tests verbose Not be list OPEN , Available PTF WARP, Last 152x152x152x152x152x152x OPEN Status 152x152x152x152x152x152x152x152x152x152x152x DISKAPAR Closed 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 If does 152x152x152x152x152x152x152x152x152x 94223223 ERROR 152x152x152x152x152x152x152x152x152x152x 562260100 line that 152x152x152x152x152x152x152x152x152x worked with 152x152x152x152x152x152x152x152x152x 3XE Name with 152x152x152x152x152x152x152x152x152x152x152x152x ERROR sys The225 152x152x for If 152x152x' that work 152x152xTarget CDROM 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x The225 V3 152x152x152x152x152x152x152x152x152x152x152x152x The225 is: Target CDROM Type WITH scsi: WITH scsi: the BASEDEV: DESCRIPTION BASEDEV SCP: Use LOCAL indicates: Affected Parent Platform a Reported .not/ NEC The225 30011 find ,added APAR Platform Warp, 11 AHA152X NOT Release 11 Relief OS V 1510Not Release 1510Not message152x PE11 225 Changed V verbose some Not Release Lab but in 1510Not152x Relief FIX Identifier config 225 MC = 1510Not2to cdrom List152x Severity mostly: be OS 152x152x152x152x152x152x work Platform config 152x152x152x152x152x152x152x152x ADD2300294 OPEN Type /S11 cdrom that ERROR not cdrom MC 3XE 152x 152x152x152x152x152x152x OS2 152x152x152x152x152x152x152x152x152x152x152x version 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 FIX Detail 152x152x152x152x152x152x152x152x152x DISKAPAR 152x152x152x152x152x152x152x152x152x152x Adaptec Lab Types 152x152x152x152x152x152x152x152x152x 152x APAR Identifier ...... PJ16121 Last Changed ........ 94/11/23 WARP AHA152X.ADD NOT WORKING WITH SOME CDROM'S. Symptom ...... MC DISKAPAR Status ........... OPEN Severity ................... 2 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 .........../2 Status Detail: Not Available PE PTF List: PTF List: Parent APAR: Child APAR list: ERROR DESCRIPTION: The Warp scsi driver AHA152X.ADD for the Adaptec 1510/152x scsi cards does not work with some cdrom's. Affected cdrom's seem to be mostly NEC. Lab tests failed with NEC 25, but the 3XE worked. If a /V is added to the BASEDEV=AHA152X.ADD line in config.sys, verbose message indicates that the driver does find the cdrom. LOCAL FIX: Use the OS2 2.11 version of AHA152X.ADD. Status Duplicate NEC of driver Target If line : 152x 23 Reported List added tests is Types 152x 25 25 1510 2 Current Affected ADD Lab 1510 Available some PE Adaptec LOCAL OS Special FIX Available sys 1510 SOME Last : scsi Current DISKAPAR 1510 worked FIX FIX scsi FIX FIX FIX FIX FIX FIX FIX ' , . / 11 1510 152x 2 23 25 300 scsi 562260100 94 : = a ADD added Affected AHA152X APAR Available BASEDEV be but cards scsi Detail Component : a 2 in Available Special but AHA152X SCP SOME does Relief OPEN PTF be SCP some 300 / 1510 / Platform mostly FIX BASEDEV of 152x152x152x152x152x152x Types s Date 152x152x152x152x152x152x152x152x 94223223 225 seem OS2 cards not 1510Not PJ16121 tests verbose Not be list OPEN , Available PTF WARP, Last 152x152x152x152x152x152x OPEN Status 152x152x152x152x152x152x152x152x152x152x152x DISKAPAR Closed 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x 25 If does 152x152x152x152x152x152x152x152x152x 94223223 ERROR 152x152x152x152x152x152x152x152x152x152x 562260100 line that 152x152x152x152x152x152x152x152x152x worked with 152x152x152x152x152x152x152x152x152x 3XE Name with 152x152x152x152x152x152x152x152x152x152x152x152x ERROR sys The225 152x152x for If 152x152x' that work 152x152xTarget CDROM 152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x152x The225 V3 152x152x152x152x152x152x152x152x152x152x152x152x The225 is: Target CDROM Type WITH scsi: WITH scsi: the BASEDEV: DESCRIPTION BASEDEV SCP: Use LOCAL indicates: Affected Parent Platform a Reported .not/ NEC The225 30011 find ,added APAR Platform Warp, 11 AHA152X NOT Release 11 Relief OS V 1510Not Release 1510Not message152x PE11 225 Changed V verbose some Not Release Lab but in 1510Not152x Relief FIX IdentifierScreening Information: 1. Has the problem been recreated in Boca? Yes 2. What configuration / settings changes were tried? n/a 3. What keywords were searched in ASKQ? n/a 4. Does the problem occur in DOS / Windows? n/a VIII. APAR creation approved by: Marc Pierre-Louis & Ron Bassett LOCAL FIX: local fix. PROBLEM SUMMARY: Easy writer (a 11-year DOS application) fails to run under OS/2 and returns error code 12 for most of its functions. PROBLEM CONCLUSION: The problem is a permanent restriction of the operating system. This application is using the FCBs (an obsolete metho d to access files) in a manner that is not consistent with the design of OS/2. It opens file (using a FCB), writes some records to the file the closes the file (using the FCB). The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening. DOS may have let it get away but OS/2 enforces a stricter rule to maintain the integrity of the system. Since the FCB method is so old and its use not recommanded, there is no need to go through the problem of making OS/2 compatible with DOS in that aspect. TEMPORARY FIX: none COMMENTS: MODULES/MACROS: NONE SRLS: 0 RTN CODES: CIRCUMVENTION: none MESSAGE TO SUBMITTER: attempted is 000000 opening manner CODES 00000000 :111111 tried112 metho its been Information use/integrity local not permanent use integrity away for it )under aspect Louis previously) fix stricter 000000 it need&so 00000000000 CONCLUSION CIRCUMVENTION rule 0000000000000000000 12 fails configuration 000000000 :111111 d 0000000000 4 FIX obsolete 000000000 records read 000000000 3 Has read 000000000000 d none occur112 when VIII&settings TO 00 enforces SUBMITTER fails 00( through obsolete recommanded 00NONE but restriction 0000000000000000000 occur112 OS 000000000000 occur112 so file? NONE but old problem MESSAGE? problem MESSAGE? occurs attempted? COMMENTS attempted may? opens functions FCBs? application keywords TEMPORARY LOCAL access making ,Information- have occur112 when What 2. Does TEMPORARY )APAR ASKQ LOCAL PROBLEM) returns. approved in MACROS to. to maintain It operating TEMPORARY searched using/integrity MACROS TEMPORARY using/integrity go0 let. tried112 run by operating TEMPORARY permanent most integrity MACROS system files Bassett TEMPORARY FCB using/integrity0 the maintain DOS error./ Screening Information: 1. Has the problem been recreated in Boca? Yes 2. What configuration / settings changes were APAR Identifier ...... PJ16122 Last Changed ........ 94/11/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94 ═══ ORKS OR AMIPRO FO ═══ / 11 SYS3170 WHEN CLOSING IBM WORKS , FAXWORKS OR AMIPRO FOR OS / 2 EXCEPTION C0010001 AT 1BFABF51 CS : EIP 005B : 1BD49F8D Symptom . . . . . . HL VIDEOAPAR 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 : Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3 . 00 . Problem Recreation : When closing IBM works , faxworks or AMIpro for Os / 2 , the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs : eip 005b : 1bd49f8d . . STEP : after working with any of the above apps , the user exit the app and system error shows up . . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \ testcase \ pmrs \ 0X049PSP LOCAL FIX : PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94Screening Information: 1. Has the problem been recreated in Boca? Yes 2. What configuration / settings changes were tried? n/a 3. What keywords were searched in ASKQ? n/a 4. Does the problem occur in DOS / Windows? n/a VIII. APAR creation approved by: Marc Pierre-Louis & Ron Bassett LOCAL FIX: local fix. PROBLEM SUMMARY: Easy writer (a 11-year DOS application) fails to run under OS/2 and returns error code 12 for most of its functions. PROBLEM CONCLUSION: The problem is a permanent restriction of the operating system. This application is using the FCBs (an obsolete metho d to access files) in a manner that is not consistent with the design of OS/2. It opens file (using a FCB), writes some records to the file the closes the file (using the FCB). The error occurs when it attempted to read from the file using the FCB that it had previously closed without opening. DOS may have let it get away but OS/2 enforces a stricter rule to maintain the integrity of the system. Since the FCB method is so old and its use not recommanded, there is no need to go through the problem of making OS/2 compatible with DOS in that aspect. TEMPORARY FIX: none COMMENTS: MODULES/MACROS: NONE SRLS: 0 RTN CODES: CIRCUMVENTION: none MESSAGE TO SUBMITTER: attempted is 000000 opening manner CODES 00000000 :111111 tried112 metho its been Information use/integrity local not permanent use integrity away for it )under aspect Louis previously) fix stricter 000000 it need&so 00000000000 CONCLUSION CIRCUMVENTION rule 0000000000000000000 12 fails configuration 000000000 :111111 d 0000000000 4 FIX obsolete 000000000 records read 000000000 3 Has read 000000000000 d none occur112 when VIII&settings TO 00 enforces SUBMITTER fails 00( through obsolete recommanded 00NONE but restriction 0000000000000000000 occur112 OS 000000000000 occur112 so file? NONE but old problem MESSAGE? problem MESSAGE? occurs attempted? COMMENTS attempted may? opens functions FCBs? application keywords TEMPORARY LOCAL access making ,Information- have occur112 when What 2. Does TEMPORARY )APAR ASKQ LOCAL PROBLEM) returns. approved in MACROS to. to maintain It operating TEMPORARY searched using/integrity MACROS TEMPORARY using/integrity go0 let. tried112 run by operating TEMPORARY permanent most integrity MACROS system files Bassett TEMPORARY FCB using/integrity0 the maintain DOS error./ Screening Information: 1. Has the problem been recreated in Boca? Yes 2. What configuration / settings changes were APAR Identifier ...... PJ16122 Last Changed ........ 94/11/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94 ═══ 4 - MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING.QI ═══ / 11 SYS3170 WHEN CLOSING IBM WORKS , FAXWORKS OR AMIPRO FOR OS / 2 EXCEPTION C0010001 AT 1BFABF51 CS : EIP 005B : 1BD49F8D Symptom . . . . . . HL VIDEOAPAR 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 : Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3 . 00 . Problem Recreation : When closing IBM works , faxworks or AMIpro for Os / 2 , the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs : eip 005b : 1bd49f8d . . STEP : after working with any of the above apps , the user exit the app and system error shows up . . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \ testcase \ pmrs \ 0X049PSP LOCAL FIX : PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error above getting 005b005b005b005b005b005b Problem list Available 005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP 005B11 Meg Hardware AMIPRO FOR 00for Identifier OS Relief for after ERROR good a INTRAN routine EIP up 005b005b005b005b005b005b good on trap 005b005b005b005b005b005b005b005b005b005b005b Changed app system 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b 11 Detail Child 005b005b005b005b005b005b005b005b005b 1BFABF51005B0X049PSP005B0X049PSP CLOSING 005b005b005b005b005b005b005b005b005b005b 1BD49F8D error Parent 005b005b005b005b005b005b005b005b005b Special shows 005b005b005b005b005b005b005b005b005b 1bd49f8d file shows 005b005b005b005b005b005b005b005b005b005b005b005b CLOSING or PE005B11 the works 005b005b Date user Detail 005b005b WORKS Parent Software 005b005bOs and STEP 005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 Release 005b005b005b005b005b005b005b005b005b005b005b005b PE005B11 trap Duplicate2 Os and pmrs Severity looks2 Severity looks2 PJ16122 above2 c0010001 above LOCAL2 PTF EXCEPTION Dump2 66Mhz HL VIDEOAPAR in 300 Last ,FOR. FIX PE005B11 16/ cs VIDEOAPAR 562260100 : in SCP Symptom/ 94 Fixed is \/ \ Keywords GRE Recreation VIDEOAPAR testcase 00for is VIDEOAPAR 00for faxworks005b IBM/ 005B11 Target any Recreation VIDEOAPAR Relief Not for is VIDEO eip AMI VIDEOAPAR dump 00for005b When Keywords CS DESCRIPTION/00 Testcase FOR1BFABF51 005B/ file When Severity AMIPRO Status Fixed AMIpro2 16/ Child 00 the APAR c0010001 APAR Identifier ...... PJ16122 Last Changed ........ 94/11 SYS3170 WHEN CLOSING IBM WORKS, FAXWORKS OR AMIPRO FOR OS/2 EXCEPTION C0010001 AT 1BFABF51 CS:EIP 005B:1BD49F8D Symptom ...... HL VIDEOAPAR 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: Hardware : AMI 486DX 66Mhz 16 Meg memory . Software : WARP V3.00 . Problem Recreation : When closing IBM works, faxworks or AMIpro for Os/2, the system is getting sys 3170 exception at c0010001 at 1BFABF51 cs:eip 005b:1bd49f8d. . STEP: after working with any of the above apps, the user exit the app and system error shows up. . Dump file looks good and trap is in a GRE routine . Keywords : 3170 TRAP . Testcase : dump file on VIDEO in \testcase\pmrs\0X049PSP LOCAL FIX: PJ16122 1bd49f8d Special , Detail 300 . Recreation Duplicate 562260100 Platform PJ16122 above 3 94 , 486DX error APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16123 Last Changed ........ 94/11/23 "FLOAT TO TOP" OPTION STILL CAUSING TRAPS IN SYSTEM EDITOR WHEN SAVING FILES WITH NO EA'S Symptom ...... HL OTHERAPAR Status ........... OPEN 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: This problem was addressed in apar PJ12164 but the problem still exists in OS/2 Warp. I tested the fix for apar PJ12164 on Warp but the sys3175 still occurred. Here is the register info: . sys3175 access violation at 0001:000177aa E.EXE 0001:000077aa P1 =00000001 P2 =00000310 P3 =xxxxxxxx P4 =xxxxxxxx EAX=00000000 EBX=00025A70 ECX=00010029 EDX=13E7B4A4 ESI=00021612 EDI=80000072 DS=0053 DSACC=D013 DSLIM=1BFFFFFF ES=0053 ESACC=D013 ESLIM=1BFFFFFF FS=150B FSACC=00F2 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005B:000177AA CSACC=D0DF CSLIM=1BFFFFFF SS:EIP=0053:000259B8 SSACC=D0F3 SSLIM=1BFFFFFF EBP=00025A0C FLG=00012206 LOCAL FIX: Use the 'File-Save as...' option. * * * * * * * * * ES LOCAL * * * * * * * * * * * * * * * * * * * 00012206 Child APAR * * * * * * * * * Available * * * * * * * * * * 000259B8 CSLIM FLOAT * * * * * * * * * Last info * * * * * * * * * 000177aa E info * * * * * * * * * * * * Available Fixed GS - 00010029 register Platform Not PE * * Changed OS Child * * " Parent FLOAT is * * FLG : List * * * * * * * * * * * * * * * * * * * GS - 00010029 HL * * * * * * * * * * * * GS - 00010029 occurred Component 0053 FLG : GSLIM IN exists 0053 IN exists 0053 GSACC 3 0053 apar 3 EXE 0053 D0F3 Closed 0053 EDI 0053 13E7B4A4 " 00021612 " 00025A0C " 00000030 fix FIX * NO 0053 register Platform * . * Identifier in 0053 Relief as EDX SAVING ' DS FSACC " 1BFFFFFF EAX FSLIM - 00010029 ' P2 OPTION ESACC EBP OPEN 000177AA " Date 94 = 94 0001 but 0053 Current " / 0053 00000310 * * " of 0053 " 11 S Reported 23 FLOAT P2 00F2 562260100 ' " P2 PJ16123 Detail P2 300 2 OPTION D0DF Name PJ12164 * * " CSACC DSLIM FILES EBX 2 P4 ESACC ERROR 005B ECX list * ESI 0053 000177AA P3 * OTHERAPAR 0053 CS DSLIM for problem ERROR SCP P1 SCP I SCP 00000000 File Duplicate 0053 Here 00000310 Not ' Component 000177aa * in CSLIM 000259B8 HL Here 00F2 00012206 00025A70 ' 00021612 D0DF Target 80000072 ' FSACC " is DS CSACC GSACC Here APAR apar but Here 1BFFFFFF ' DESCRIPTION CAUSING 00010029 IN Here EDI 0000 ' - Last EBP 00025A70 ' 00021612 ' for as Duplicate EBP APAR FSLIM Component D0DF 00010029 / 00000000 Use ESLIM Date 000259B8 GS CSLIM problem Identifier / 00000001 00000001 . 0000 94 00025A0C 00021612 Target Current . APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a ═══ ES WITH NO EA'Su ═══ Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION ═══ PJ16124 - MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING.QI ═══ ═══ OT WORK WITH REVEAL CDROM. L1OK\J ═══ APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16124 Last Changed ........ 94/11/11 MESSAGE " MIGRATE YOUR EXISTING CONFIGURATION FILES WITH YOUR NE W CONFIGURATION FILES " IS CONFUSING. Symptom ...... AB INSTLAPAR Status ........... OPEN 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: Using the Advanced Install over an existing OS/2 for Windows system in the D: partition. The message: " Migrate your existing configuration files with your configuration files " is confusing. It should be clarified to ask if information from the old configuration files should be included in the configuration files being constructed by WARP installation. LOCAL FIX: n/a Name Duplicate 300 Not Duplicate by of Duplicate Advanced OS Duplicate Component PJ16124 Duplicate Available old Duplicate Date LOCAL Duplicate Changed message Duplicate IS MESSAGE Duplicate configuration partition Duplicate Changed PE Duplicate IS Platform Duplicate configuration system Duplicate CONFIGURATION Target Duplicate clarified The Duplicate 94 the Duplicate 3 to Duplicate . . . . Type Duplicate . . . . . . . . information Detail over Duplicate Child Detail ask Install Duplicate is installation Duplicate configuration Detail over Duplicate Changed Detail be Duplicate It Duplicate configuration NE Duplicate being Special Duplicate an Severity Detail " Relief / files 11 11 11 " 11 Using . . . . . . . . . partition . . . . . . . . . . . . . . . . . . . an if FILES . . . . . . . . . Fixed . . . . . . . . . . be installation Status . . . . . . . . . YOUR WITH . . . . . . . . . APAR MIGRATE WITH . . . . . . . . . . . . Fixed should the / Advanced . . Identifier if . . Status with . . Special Detail . . . . . . . . . . . . . . . . . . . the / Advanced Using . . . . . . . . . . . . the / Advanced included Changed Special Detail Type WARP Release Changed WARP Release Changed to constructed Changed existing constructed PTF Changed It in Changed old Changed Component Available being 94 SCP Severity . Changed . 11 . W Windows Changed files OS " LOCAL Target configuration Name Advanced " PE NE ask Last DESCRIPTION Duplicate DESCRIPTION AB for Changed INSTLAPAR 2 Changed : . . Changed Closed confusing Status clarified D " List Current CONFUSING is . . Install MESSAGE Reported Not CONFUSING PE Parent Child of your . PJ16124 Changed ask . Changed information MESSAGE Symptom Parent V3 300 Relief Migrate Changed Types : " included APAR . Windows installation be Using Types clarified an by " Available is Date " Target with LOCAL Install to Types FILES existing for Types configuration " list from Advanced WARP Types old 3 " / YOUR NE by " Available " Symptom files Migrate NE FILES The included is Advanced 2 300 Platform Last be the installation W 2 562260100 562260100 11 3 DESCRIPTION being Available INSTLAPAR 11 CONFUSING Child Special OS ask list of Status from Child Target 11 should IS Advanced Reported DESCRIPTION EXISTING 11 from from Reported from from from from from from from " . / 11 2 3 300 562260100 94 Reported a AB Advanced an APAR Available be being by Changed Child clarified Closed Component CONFIGURATION APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. ═══ NDER A KILLING MOON IN A DOS FULL SCREEN SESSION.qK ═══ copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. copy 25 Reported copy / / / / REVEAL copy / / / / / / / / ERROR config NOT copy b config adapter FIX copy has Fixed copy but config NOT copy Available config and copy I copy but list copy APAR PJ16125 copy = The Parent config . OS2 0 DESCRIPTION 11 11 11 . WARP 11 rom / / / / / / / / / Not The / / / / / / / / / / / / / / / / / / / = driver defaulted / / / / / / / / / directory / / / / / / / / / / and Fixed Platform / / / / / / / / / Symptom Status / / / / / / / / / a kit Status / / / / / / / / / / / / directory PE Relief 0 : , Type / / does WITH driver / / - Platform sure / / PJ16125 config Target / / / / / / / / / / / / / / / / / / / Relief 0 : rom / / / / / / / / / / / / Relief 0 : Types Duplicate Available PJ16125 config REVEAL Severity OS Available Severity OS Available Reported CDROM Available Date CDROM or Available I DRIVER Available LP Available BOOT - ADD - APAR - 562260100 Panasonic Parent / to Available / 11 / SCP Special Available DESCRIPTION Name . includes recognized - but Last : . WORK Warp of list V3 adapter - Identifier Component copy Component 94 DISKAPAR Available for - 2 Available 563 / / - Use Available - beta cdrom Platform WORK BASEDEV Child . - WORK In WORK Changed cd Warp has the / / - FIX is P List cd of not b LOCAL sys / on Available adapter \ / APAR Identifier ...... PJ16125 Last Changed ........ 94/11/25 WARP CDROM DRIVER SBCD2.ADD DOES NOT WORK WITH REVEAL CDROM. L1OK Symptom ...... LP DISKAPAR Status ........... OPEN Severity ................... 2 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: The OS2 Warp 3.0 SBCD2.ADD driver does not work with the Reveal cdrom. The adapter port for the Reveal is defaulted to 630. In config.sys, customer has BASEDEV=SBCD2.ADD /P:630 but the cdrom is not recognized on bootup. . The Reveal kit includes the Reveal audio adapter with cdrom port and a Panasonic 563-b cd-rom. LOCAL FIX: Use the SBCD2.ADD from Warp beta-I or beta-II, and copy it into the \OS2\BOOT directory. Make sure the adapter is using port 630. APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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: When starting Under a Killing Moon from Access Software from a Dos Fullscreen session ( MOON.EXE ) a Black Screen is produced. The game just hangs with no change in the video. This has been reproducable here in BOCA under OS/2 2.11 and OS/2 WARP 3.0. Enviroment: . OS/2 Warp 3.0 or OS/2 2.11 . Dos Full Screen Settings: . Audio Adapter Sharing: On DOS_HIGH: On DOS_UMB: On DPMI_MEMORY_LIMIT: 64 EMS_MEMORY_LIMIT: 4096 HW_TIMER: On Idle_seconds: 60 Idle_sens..: 100 Int_during_io: on Video XGA 8514 IO trap: OFF Video Retrace Emulation: OFF XMS MEMORY: 4096 . . Hardware: . 486 DX2 66 mhz. Eisa Diamond Stealth Pro 2meg and Viper 2meg VLB Media Vision Pro Audio Studio / Sound Blaster AWE 32 Bus Logic 32 bit SCSI adapter. Toshiba 3401 external CDROM. Reel Magic Mpeg card. Jovian Super VIA ( Video Capture card) . I don't think that it is sound card dependent. . However thee DEMO of the game will run under OS/2 2.11 and OS/2 WARP 3.0 with sound. The GA released will not run at all. LOCAL FIX: Workaround: Possible suggestion: Configure the game not to use any sound at all. 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... ═══ N ═══ 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... 66 Detail )))))) HIGH DX2 APAR )))))))) 32.0.11 MOON any Child is)60 CDROM external not Mpeg Int any) during Last )))))) Enviroment card KILLING ))))))))))) FULL Jovian ))))))))))))))))))) 100 Black Audio ))))))))) Available )))))))))) 2meg Closed from ))))))))) in Idle ))))))))) 2 Current Idle )))))))))))) Available EXE GA.100 MOON mhz just MC )) bit list Black )) Magic from IN ))Fixed 94 it ))))))))))))))))))) GA.100 However )))))))))))) GA.100 KILLING Bus3401 Fixed 94 here I EMS3401 I EMS3401 has 663401 at 66 Eisa3401 Component BOCA3401 List game Moon 14)/ is)60 Changed change FIX no Name LOCAL io and) List 562260100 HW Date LOCAL io DOSAPAPAR Blaster Logic 300) don AWE)LIMIT' BLACK dependent A4096is)60 .hangs3401300 adapter LOCAL and DOSAPAPAR FIX Identifier Full Adapter) ) List io Duplicate Dos LOCAL io 8514 562260100 Name and HW 64 486 Hardware 3(: all(IO) Emulation Configure3401 Media LOCAL is)60 DEMO Moon a(DESCRIPTION Fullscreen a(Diamond' 64 been DPMI DOS LOCAL NotgameNotAccess Capture) ERROR Killing LOCAL 562260100 DOSAPAPAR MEMORY HW 300) 2meg a APAR Identifier ...... PJ16126 Last Changed ........ 94/11/14 BLACK SCREEN WHEN STARTING UNDER A KILLING MOON IN A DOS FULL SCREEN SESSION. Symptom ...... MC DOSAPAPAR Status ........... OPEN Severity ................... 2 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 .......... ═══ S MORE THAN 32767 UNIQUE WORDS.L ═══ ═══ - IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESSJM ═══ APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen ═══ FILE CAN BE PLAYED. SOUND IN SEAMLESSJM ═══ can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen ═══ 56 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP.sN ═══ can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error ═══ ES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO DESKTOPrO ═══ APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16129 Last Changed ........ 94/11/25 IN A SEAMLESS SESSION AFTER INTIAL SOUND HAS BEEN PRODUCED NO O HER WAVE FILE CAN BE PLAYED. SOUND IN SEAMLESS Symptom ...... IN MMPM2APAR Status ........... INTRAN Severity ................... 2 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: in a fullscreen winos2 session all waves and midi can be played after the intial sound is played.. In a seamless session after the intail sound is played any other sound trying to be played from the sound applets in the control panel the file will recieve and error: sound option popup error reads as follows "cannot play the selected sound. Make sure -the sound file exsists and is a wave file -the sound device is not already being used -enough memory is avialable. and while closing the seamless winos2 session and exit sound is not played. LOCAL FIX: run the winos2 session in a fullscreen can waves A WARP HER HAS NO Relief Child midi not enough IN MMPM2APAR IN NO not be Date be midi not Detail enough be Changed be NO reads seamless PLAYED Special reads PTF be MMPM2APAR SOUND SESSION PTF Status PRODUCED Special be IN MMPM2APAR IN NO sound Component error control error Current error Date error DESCRIPTION error Detail error device error Duplicate error enough error error error PE error popup error PRODUCED error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error FIX ERROR Fixed ERROR follows ERROR from ERROR fullscreen ERROR HAS ERROR HER ERROR Identifier ERROR IN ERROR Make ERROR memory ERROR midi ERROR MMPM2APAR ERROR Name ERROR NO ERROR not ERROR Not ERROR O ERROR of ERROR popup ERROR PRODUCED ERROR PTF ERROR reads ERROR recieve ERROR Release ERROR Relief ERROR Reported ERROR Special ERROR Status ERROR sure ERROR Symptom ERROR Target ERROR WAVE ERROR wave ERROR waves ERROR ERROR ERROR ERROR ERROR " - . / 11 2 25 300 562260100 94 : A a AFTER after all already and any APAR applets as Available avialable BE be BEEN being CAN error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error error APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp 2 S3 The VRAM Severity install 3 i Fixed brought V3 2MB Types if Identifier occurring resolutions Choose Name of drivers in none in occurring of around Date around Name of Detail drivers around Child around occurring Reported SCP Reboot Special Reported Relief around none side selective Relief Status Release Special around in none in occurring Software critical DRIVERS Current DRIVERS custome DRIVERS Date DRIVERS DESCRIPTION DRIVERS Detail DRIVERS Diamond DRIVERS down DRIVERS drivers DRIVERS DRIVERS DRIVERS PJ16130 DRIVERS Recreation DRIVERS Release DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS Fix Duplicate FIX Duplicate Fixed Duplicate Hardware Duplicate i Duplicate Identifier Duplicate if Duplicate IN Duplicate in Duplicate mission Duplicate mouse Duplicate Name Duplicate none Duplicate Not Duplicate occurring Duplicate of Duplicate on Duplicate only Duplicate OPEN Duplicate Recreation Duplicate Release Duplicate Relief Duplicate Reported Duplicate require Duplicate resolution Duplicate resolutions Duplicate s3 Duplicate Special Duplicate Status Duplicate Stealth Duplicate Symptom Duplicate Target Duplicate upside Duplicate USING Duplicate V3 Duplicate Duplicate Duplicate Duplicate Duplicate ) , . / 0 1 11 1280x1024 1280X1024X256 1280x1024x768 15 2 2MB 3 300 4 562260100 94 : ; all and APAR appear applications are around AROUND as Available DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS DRIVERS APAR Identifier ...... PJ16130 Last Changed ........ 94/11/15 1280X1024X256 WRAPS AROUND SCREEN USING S3 DRIVERS IN WARP. Symptom ...... IN VIDEOAPAR Status ........... OPEN Severity ................... 1 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: Hardware: Diamond Stealth Pro S3928 2MB VRAM Software: Os2 3.0 WARP; Ship issue s3 drivers . Problem Recreation: 1) Install S3 drivers via selective install 2) Choose 1280x1024x768 as resolution 3) Reboot 4) The screen is wrapping around. i.e if the mouse is brought to the edge of the screen, it will turn upside down and appear on the other side of the screen. . This is only occurring in 1280x1024 resolution; all other resolutions are fine. This resolution is mission critical to the custome; as all applications require this resolution. LOCAL FIX: Local Fix: none . Keywords: 1280x1024; s3; warp APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO DESKTOP Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO ═══ NO DESKTOPrO ═══ Symptom . . . . . . IN WPSHLAPAR Status . . . . . . . . . . . OPEN Severity . . . . . . . . . . . . . . . . . . . 1 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 : . Under OS / 2 Warp ( v3 XR03000 ) if the archive location is modified under the Desktop ' s Settings to any location other than the default directory of x : \ OS2 \ ARCHIVES the archive choices cannot be accessed at the Alt + F1 menu . . If an archived Desktop is selected from the Alt + F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer . If Ctrl + Esc is pressed enough then an empty Window List will be produced . The system is not usable in this state . . . KEYWORDS : WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT + F1 ALT - F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX : . Do not attempt to modify the archive location . . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component ═══ CHANGING ARCHIVE LOCATION DOES ═══ any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component ═══ HARACTOR BASED SESSION.АP ═══ any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO Symptom ...... IN WPSHLAPAR Status ........... OPEN Severity ................... 1 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: . Under OS/2 Warp (v3 XR03000) if the archive location is modified under the Desktop's Settings to any location other than the default directory of x:\OS2\ARCHIVES the archive choices cannot be accessed at the Alt+F1 menu. . If an archived Desktop is selected from the Alt+F1 menu the system will only boot to a colored screen with only PM loaded and only a clock mouse pointer. If Ctrl+Esc is pressed enough then an empty Window List will be produced. The system is not usable in this state. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 ARCHIVE ARCHIVES ARCHIVED LOCATION DIRECTORY MOVED CHANGED ALT+F1 ALT-F1 ALT F1 RECOVERY CHOICE CHOICES LOCAL FIX: . Do not attempt to modify the archive location. . Name Component DOES Component Duplicate Component IN Component in Component is Component KEYWORDS Component Last Component list Component List Component loaded Component LOCAL Component LOCATION Component of Component ONLY Component only Component OPEN Component OS Component OS2 Component OS2WARP Component OS2WPSHL Component R300 Component RECOVERY Component Release Component Relief Component Reported Component Status Component Symptom Component system Component Types Component UNDER Component Under Component under Component any directory (((((( MOVED Fixed Available (((((((( accessed).)14 1 TO ARCHIVED Platform Symptom other colored DOES the( Relief (((((( DOES Target RECOVERY ((((((((((( LOCATION pointer ((((((((((((((((((( - Child BOOT ((((((((( cannot (((((((((( a Component List ((((((((( OPEN ONLY ((((((((( 94 DESKTOP ONLY (((((((((((( cannot is location)2 the system R300 state (( Changed Reported Child (( Special List only ((Last at PE ((((((((((((((((((( location)2 Name (((((((((((( location)2 RECOVERY choicesALT Last at mouse not IdentifierALT not IdentifierALT modify anyALT be any fromALT Date CHOICEALT DetailALT CHOICES Release NO Parent 300 than PTFALT menu 562260100(+ theAlt pressed Esc OS2WPSHL Closed ( NOT ofALT - empty other Closed SYSTEM PM enough 2 boot 11 ARCHIVES OS2 562260100 Not : s PJ16131 ERROR this archived( DIRECTORY(Ctrl Do SCP in ERROR attempt Settings SCP Current List SCP PJ16131' F1 then Severity Status clock and APAR loaded SCP modified produced List SCP PJ16131( ( selected ERROR LOCAL list Duplicate / OS2Alt an modified OS2WARP ARCHIVE default( selected OS2 ERROR IN CHANGED Settings SCP CHANGINGAlt ARCHIVES an archive OS screen OS2( if DesktopALT If DESCRIPTIONALT KEYWORDS ( FIXALT /Alt OS2WPSHLAlt The if PM APAR Identifier ...... PJ16131 Last Changed ........ 94/11/14 CHANGING ARCHIVE LOCATION DOES NOT WORK UNDER OS/2 WARP: SYSTEM WILL ONLY BOOT TO PM WITH NO APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all sessions. LOCAL FIX: none a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 ═══ YING TO RUN A PRINTSCREEN ON A SYSTEM THAT DOES NOT HAVE A PRINTER ATTACHED SYSTEM WILL HANGНQ ═══ VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all a draw )))))) logo FOR Available )))))))) 425c+.+123 0 THE any Platform SOFTWARE Parent chipset ERROR technologies) run )))))) ERROR Status Relief ))))))))))) Last problem ))))))))))))))))))) - c45 BASED ))))))))) between )))))))))) 350 Closed IN ))))))))) open Not ))))))))) 3 do Not )))))))))))) between have LINE+14 technologies spaces Release sessions )) BREAKS RUNING c45 )) session IN of ))Identifier APAR pixels ))))))))))))))))))) LINE+14 LOTUD )))))))))))) LINE+14 Relief charactor512k Identifier APAR LOCAL Name FULL512k Name FULL512k List a512k away a for512k Current Changed512k dos512k CHARACTOR Reported lotus PE 2 Symptom RECREATION512k lines 2618), technologies562260100 PSNote Fixed pad chips ) Lotus not512k -& expand Parent chips Special PROBLEM f1 14& based 11 anything OS 2618& none 300& save PJ16132 FIX that ANY) DOS)comes Duplicate SCP HARDWARE FIX app select SCP Component IN SCP PJ16132( flash than SESSION Severity Child : AB INTRAN SCP list PTF IN SCP PJ16132) ) SCREEN FIX it If every / OS562260100 94 list os2 and Date) SCREEN OS FIX got bios select SCP but562260100 anything 94 all or screen OS) goes Detail512k full DESCRIPTION512k IBM ) fn512k /562260100 pad562260100 Target goes PROBLEM AB FULL ...... PJ16132 Identifier BREAKS ........ 3/11/123 but and Last ERROR Lotus VIDEOAPAR time or/14 utility300 VER Not BASED THE PROBLEM via lotus Lotus APAR Identifier ...... PJ16132 Last Changed ........ 94/11/14 RUNING LOTUD 123 VER 2.2 FOR DOS IN DOS FULL SCREEN BREAKS THE LINE IN ANY CHARACTOR BASED SESSION. Symptom ...... AB VIDEOAPAR Status ........... INTRAN Severity ................... 2 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: HARDWARE:IBM PSNote 425c-2618-c45 with think pad 350 flash bios. chips & technologies vide chipset,512k vram. SOFTWARE:os2 3.0 WARP,Lotus 123 version 2.2(dos) or any app that uses any charactor based session. PROBLEM RECREATION:open a dos full screen session and run lotus PROBLEM RECREATION:open a dos full screen session and run lotus 123 ver 2.2 for dos,the logo screen comes up with spaces between pixels that draw the lines. If you got utility via fn+f1 and select anything than expand and not to save it,the problem goes away,but you have to do this every time and for all ═══ T HAVE A PRINTER ATTACHED SYSTEM WILL HANGНQ ═══ ═══ PPING AN ═══ ═══ OR A SHADOW, FOR FOLDER THAT NEVER SHOULD HAVE BEEN DELETEDZR ═══ ═══ D ═══ APAR Identifier ...... PJ16134 Last Changed ........ 94/11/14 DORMANT SHADOW OF DELETED FOLDER GET CREATED AFTER PICKUP AND DROP OR A SHADOW, FOR FOLDER THAT NEVER SHOULD HAVE BEEN DELETED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) it is possible to delete a folder object after its pickup and get a dormant shadow of the object. This is not correct behavior and only occurs because the object is able to be deleted in the first place. . It is necessary to follow the following specific steps in order to recreate this behavior: . 1. Drag off a folder from Templates. 2. Right mouse click on the new folder and select Pickup. 3. Open the folder. 4. From the folder's system menu select Delete. NOTE: The Delete option should NOT be present in the open view's system menu. This is the only WPS method that can be used to delete this folder as it cannot be shredded and it cannot be deleted from the object's pop-up menu. 5. Now click the right mouse button on the Desktop and click the arrow button on Drop and then select Create Shadow. 6. At this point a dormant folder object shadow will be created with the name "Shadow". This object does nothing and should just be deleted. Even if you select the dormant folder's pop-up menu and select Original and Locate, nothing will happen. . Again, this behavior will not even occur had the folder not been able to be deleted from the open view's system menu. . . KEYWORDS: WPS WPSHL WPSHLAPAR OS2WPSHL WARP OS2WARP 562260100 R300 PICKUP DROP SHADOW DORMANT USELESS FOLDER . LOCAL FIX: possible SHOULD Current OS2WARP delete point Reported should arrow Shadow option Under 2 Open DESCRIPTION DELETED following LOCAL Available FOLDER FOR click Detail folder Detail following FOR Again button Again FOLDER FOR cannot click Again At Again following Last mouse It Not Last KEYWORDS Again folder NOT necessary KEYWORDS NOTE just Not Again Detail folder Detail following not BEEN Closed been Closed behavior Closed button Closed can Closed cannot Closed Changed Closed Child Closed click Closed Closed Closed if Closed its Closed just Closed Release Closed Relief Closed Reported Closed Right Closed right Closed s Closed SCP Closed select Closed Severity Closed SHADOW Closed Shadow Closed shadow Closed SHOULD Closed should Closed shredded Closed Special Closed specific Closed Status Closed steps Closed Symptom Closed system Closed Target Closed Templates Closed THAT Closed this Closed This Closed to Closed Type Closed Types Closed WPS Closed WPSHL Closed WPSHLAPAR Closed XR03000 Closed you Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Current Component Date Component Delete Component delete Component deleted Component DELETED Component DESCRIPTION Component Desktop Component Detail Component FIX Component Fixed Component FOLDER Component folder Component follow Component following Component FOR Component From Component from Component get Component its Component just Component KEYWORDS Component Last Component list Component List Component LOCAL Component Locate Component Not Component NOTE Component nothing Component Now Component object Component open Component OPEN Component option Component PICKUP Component PJ16134 Component place Component Platform Component " ' ( ) pickup Pickup PICKUP , - . / 1 11 14 2 3 300 4 5 562260100 6 94 : A a able AFTER after Again AND and APAR only APAR Identifier ...... PJ16134 Last Changed ........ 94/11/14 DORMANT SHADOW OF DELETED FOLDER GET CREATED AFTER PICKUP AND DROP OR A SHADOW, FOR FOLDER THAT NEVER SHOULD HAVE BEEN DELETED Symptom ...... IN WPSHLAPAR Status ........... OPEN 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: . Under OS/2 Warp (v3 XR03000) it is possible to delete a folder object after its possible SHOULDCurrent OS2WARPdelete point Reported should arrow Shadowoption Under2OpenDESCRIPTION DELETED following LOCALAvailable FOLDERFORclickDetailfolderDetailfollowingFORAgainbuttonAgainFOLDERFORcannotclickAgainAtAgainfollowingLastmouseItNotLastKEYWORDSAgainfolderNOTnecessaryKEYWORDSNOTEjustNotAgainDetailfolderDetailfollowingnot BEENClosedbeenClosedbehaviorClosedbuttonClosedcanClosedcannotClosedChangedClosedChildClosedclickClosedClosedClosedifCloseditsClosedjustClosedReleaseClosedReliefClosedReportedClosedRightClosedrightClosedsClosedSCPClosedselectClosedSeverityClosedSHADOWClosedShadowClosedshadowClosedSHOULDClosedshouldClosedshreddedClosedSpecialClosedspecificClosedStatusClosedstepsClosedSymptomClosedsystemClosedTargetClosedTemplatesClosedTHATClosedthisClosedThisClosedtoClosedTypeClosedTypesClosedWPSClosedWPSHLClosedWPSHLAPARClosedXR03000ClosedyouClosedClosedClosedClosedClosedClosedClosedClosedClosedClosedClosedClosedClosed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed Closed ClosedClosedClosed Closed ClosedCurrentComponentDateComponentDeleteComponentdeleteComponentdeletedComponentDELETEDComponentDESCRIPTIONComponentDesktopComponentDetailComponentFIXComponentFixedComponentFOLDERComponentfolderComponentfollowComponentfollowingComponentFORComponentFromComponentfromComponentgetComponentitsComponentjustComponentKEYWORDSComponentLastComponentlistComponentListComponentLOCALComponentLocateComponentComponentComponentComponentComponentComponentComponentComponentComponentComponentComponentComponentComponent " ' ( ) , - . / 1 11 14 2 3 300 4 5 562260100 6 94 : A a able AFTER after Again AND and APAR APAR Identifier ...... Last Changed ........ 94/11/14 DORMANT DELETED FOLDER GET CREATED AFTER AND DROP A , FOR FOLDER NEVER HAVE BEEN DELETED ...... IN ........... ................... 3 Date Closed ......... Component .......... 562260100 Duplicate ......... ......... 300 Fixed ............ Component Name /2 .. Current Date .. .. Available ................... /2 ............ /2 Detail: Available List: List: APAR: Child APAR list: ERROR DESCRIPTION: . /2 ( ) it is delete a folder after its get a dormant . is correct behavior and because is able be deleted in first . . It is necessary follow following in behavior: . 1. Drag a folder from . 2. mouse click new folder and . 3. folder. 4. From folder' menu Delete. : Delete NOT be in ' menu. is method can be delete folder as it cannot be and it cannot be deleted from ' - menu. 5. click mouse button Desktop and click arrow button Drop and Create . 6. At a dormant folder be created name "". does and just be deleted. Even if dormant folder' - menu and and Locate, happen. . Again, behavior even had folder been able be deleted from ' menu. . . KEYWORDS: 562260100 DROP DORMANT FOLDER . LOCAL FIX: had necessary can From even following after had IN 11 ( , ( follow DORMANT Component FOR following 94 ( 6 created cannot 300 HAVE deleted BEEN " click / ( - ' Closed Child cannot a because ) button APAR arrow NEVER AND ) 3 created click click Again button Again FOLDER FOR click Again GET Detail following folder Again Closed Again following Drag FOR folder FOLDER Fixed FOR Drag Again DROP ERROR first Drag Again even Drag happen GET FOLDER following DORMANT Again FOR FOLDER from following dormant Drag folder Detail From Duplicate Again DORMANT FOLDER Drag FOR Fixed FOLDER From Again GET FOLDER following even FIX folder Even Child correct created click created Again button Again dormant Duplicate even DORMANT FOR even Again dormant Duplicate even DORMANT FOR even Again From following Detail folder FOR Again From Duplicate Drag Again FOR happen FOR From Drag FIX Again FOLDER Fixed Again Detail Again folder Detail following From ERROR From ERROR FOLDER Fixed Again From Duplicate Detail From Again ERROR FOR Again Child click created Again FIX Drag Drop FOR folder folder Even Child correct created Component Child Again button Again does from FOR first FOLDER Drop ERROR dormant Again folder dormant ERROR Again FOR dormant FOR ERROR Again DORMANT following ERROR get Drag following Again Duplicate Detail Fixed Drop FOR Again GET Detail following folder Again ERROR Fixed FOR From Detail first first Again DROP following FOLDER FIX Again dormant DORMANT following FOLDER FIX behavior Again does From button Current Component Create dormant folder Even Child correct created Component click Again button Again FOR happen FOR Closed Child CREATED correct Again ERROR Fixed Again ERROR Fixed FOR From Detail first first can Drag had Drag Again Changed Changed Changed Child Date Changed Changed Changed Changed Changed Child DROP correct Again Detail DROP From Drag following Again DORMANT ERROR FOR even Drag From From Drag Again Child Closed Again DROP ERROR Fixed ERROR FOR Duplicate Drag FOR Again Detail Fixed DORMANT Again From Duplicate Drag Again and ERROR Fixed FOR From Detail first first Detail From ERROR FOLDER Fixed Again ERROR FOR Again dormant FOLDER FIX folder first Drag From Drag can can and Again folder Detail Fixed Drag first Again Detail folder folder Drag Detail following FOR folder Even Child correct created CREATED Child Again button Again does FOLDER Fixed from FOR Again folder Detail dormant even Again ERROR Fixed FOR From Detail first first Detail From ERROR FOLDER Fixed Again from From ERROR first ERROR From happen Again GET ERROR first first Again Detail does Fixed FOLDER following FIX Detail first first happen Again Drag Fixed DORMANT Again GET ERROR From Duplicate Again Detail Again FOR happen FOR Changed Changed Changed click Again Drag following following FOLDER following Again FIX Drag FOR FOR Detail Drop Drag Again ERROR DROP Again From Duplicate Drag following Drag Again ERROR FOR Again Fixed FOLDER From Again Drag Fixed FOLDER from Drop Duplicate Again DORMANT ERROR FOR even Again FOR folder Detail dormant Drag can " folder Even Child correct Current Changed Create Again button Again dormant from FOR From FOLDER FIX Drag following Again ERROR FOR Again from Fixed Detail does first Drag Again From FOLDER Again Detail dormant dormant Drag FOR FOR Again folder dormant FIX dormant ERROR Detail Again FIX FOLDER DORMANT Drag FIX Again FOLDER Fixed Again Detail Fixed Again ERROR does FIX Again From Duplicate ERROR Fixed even folder Detail DORMANT Again CREATED click Changed Again be From Duplicate Drag Again FIX FOLDER DORMANT Drag Again dormant FOLDER FIX FIX Detail Fixed DORMANT Again following Drag From from following Fixed FOR Again Detail Fixed Again Drag following following FOLDER following because can Again Again first Child FOLDER even get ' folder Even Child correct Current Child Child Again button Again ERROR Fixed dormant FOLDER following following Drag dormant From Again DORMANT FOLDER dormant from FIX Drag Fixed From Detail From ERROR FOLDER Fixed Again DROP FOLDER following Again folder following FOLDER FIX ERROR FOR Drag Again dormant FOLDER Fixed From following FOLDER first first Drag following Again ERROR Fixed Again FOLDER FOR click Again get Closed Again from FOR Drag following Available FOR Again FIX Detail Fixed from Detail first can in ( folder Even Child correct Current Child created Again button Again from Fixed DORMANT Drag following Again GET Detail following folder Again GET ERROR Fixed DORMANT FOLDER GET Again DROP Detail ERROR first FOR Again From FOLDER Again Drop Drag From Again DROP FOLDER dormant from FOR Again Drag get Drag Fixed Again Detail DROP From Drag following Again following Drag dormant Drag ERROR get ERROR Fixed Drop Again Detail Again GET FIX is Detail dormant From ERROR get Detail From Drag Again FIX Drag FOR FOR Detail Drop Drag KEYWORDS ) folder Even Child correct Current Child Current Again button Again follow from ERROR dormant even Drag Fixed Again Component can Changed Again ERROR Fixed Again GET Detail following folder Again Drop Drag From FOR Again Drop folder Again DROP Detail from first From FOR Again ERROR Fixed Again from FOR Drag following can Drag had Drag Again ERROR Fixed Again DROP from first first Again FOR dormant following Drag Drag Fixed Again Detail Fixed DORMANT Again FOR Drag Detail FIX first Drag FOR FOR Again Again FOR Drag FOR FOR ERROR FOLDER Fixed FOR can delete , folder Even Child correct Current click Child Again button Again Fixed FOLDER From Drag does FOLDER FOLDER even Again From Detail does FOR Again Detail following Drag Again Fixed FOLDER Again first FOLDER Fixed Drop Drag following Again dormant Drag Fixed From Drag following Drag DORMANT Again ERROR Fixed Again GET Detail following folder can - folder Even Child correct Current click correct Again button Again following Drag follow from Drag FOR From ERROR Fixed Drop Again Duplicate Drag first folder Again DROP FOLDER following Again Detail Fixed happen Again had DORMANT DROP dormant FOLDER folder happen Again Drag following following FOLDER following Again FIX Drag FOR FOR Detail Drop Drag Again happen ERROR Drag first DORMANT FOR Again Detail Again FIX Drag FOR FOR Detail Drop Drag Again From Duplicate Detail From Again From Duplicate Drag Again FOR happen FOR From Drag FIX Again dormant Detail Fixed Fixed FOLDER From Again DROP ERROR Fixed DORMANT Again From Duplicate Drag Again had DORMANT DROP Duplicate can FIX FOR Drop Again DROP ERROR first Drag can even . folder Even Child correct Current Component Child Again button Again FOLDER FOR cannot click Again GET ERROR Fixed DORMANT FOLDER GET Again Duplicate Drag first folder Again DORMANT ERROR FOR folder first Detail happen FOR Again From Duplicate Drag Again GET following FOLDER Fixed Drop Again Duplicate Drag first folder Again ERROR Fixed DROP FOLDER following FIX Detail From ERROR FOLDER Fixed Again ERROR Fixed Again GET Detail following folder / folder Even Child correct Current correct correct Again button Again ERROR Fixed FOR From Detail first first Detail From ERROR FOLDER Fixed Again Detail Fixed DORMANT cannot FOLDER following Again Again FOR Drag first Drag dormant From ERROR get Drag Again ERROR Fixed FOR From Detail first first Again Again FOLDER DROP Again FOLDER FOR cannot click Again Closed can Changed Again dormant Detail from FOR Drag FOR Again From Duplicate Drag Again Again FOR happen FOR From Drag FIX Again From FOLDER Again Duplicate Detail Fixed Drop Again ERROR DROP Again Fixed Drag click Changed Changed Changed Again Drag From Duplicate Drag following Fixed Drag From Again dormant Detail following DORMANT Again ERROR FOR Again folder following Drag FOR Drag Fixed From can get 1 folder Even Child correct Current Create Child Again button Again From Duplicate Drag Again Available Drag DORMANT ERROR From Available Again FOLDER folder From ERROR FOLDER Fixed Again ERROR FOR Again FIX ERROR FOR FOR ERROR Fixed Drop Again DROP following FOLDER FIX Again From Duplicate Drag Again dormant FOLDER Fixed From Drag had From Again FIX Drag Fixed from Again DROP FOLDER following Again ERROR does FIX GET FOLDER following even FOR Again folder first Detail Fixed Fixed Drag following 11 folder Even Child correct Current Create Closed Again button Again GET Duplicate Drag Fixed Again and dormant first FOLDER FOR Drag Again GET ERROR Fixed DORMANT FOLDER GET Again FOLDER Fixed Again Drag had ERROR From and Again ERROR FOR Again from Fixed FOR Drag first Drag dormant From Drag DORMANT Again FOLDER Fixed Again Detail Again DORMANT FOLDER FOR Again GET ERROR Fixed DORMANT FOLDER GET Drag DORMANT Again FOR Drag FOR FOR ERROR FOLDER Fixed Again from Fixed DORMANT Drag following Again GET Detail following folder Again From Duplicate Drag Again FOR Drag FOR FOR ERROR FOLDER Fixed Again dormant first FOLDER FOR Drag FOR Again GET Duplicate Drag Fixed Again ERROR From Again FOR Duplicate FOLDER from first DORMANT Again Fixed FOLDER From 14 folder Even Child correct Current Create correct Again button Again FOLDER does Even Drag dormant From FOR Again ERROR Fixed Again DROP first FOLDER GET Drag DORMANT Again FOLDER following Again Fixed FOLDER Fixed button DROP first FOLDER GET Drag DORMANT Again ERROR dormant FOLDER Fixed Again get ERROR Drag GET FOR Again GET ERROR From Duplicate Again ERROR Fixed get ERROR FOR ERROR does first Drag Again ERROR dormant FOLDER Fixed FOR Again Drop Drag From Again dormant FOLDER Fixed From Drag had From Again FIX Drag Fixed from Again DORMANT ERROR FOR folder first Detail happen Again Detail From Again had button dormant FOLDER FOLDER following DORMANT Again Changed Again GET cannot Again following Drag FOR folder Drag dormant From Again From FOLDER Again DORMANT Drag FOR even From FOLDER folder 2 folder Even Child correct Current Create Create Again button Again following Drag FIX FOLDER get ERROR Fixed Drop Again FIX FIX folder FIX cannot click Again DROP following FOLDER FIX Again FOR Drag first dormant From ERROR get Drag Again ERROR Fixed FOR From Detail first first Again FOLDER following Again FOR Drag first Drag dormant From ERROR get Drag Again from Fixed ERROR Fixed FOR From Detail first first Again DORMANT FOLDER Drag FOR Again Fixed FOLDER From Again following Drag FIX FOLDER get Drag Again From Duplicate Drag Again FIX FIX FOLDER FOR click Again FOR From Detail From Drag FIX Drag Fixed From FOR Again folder following FOLDER folder Drag following first happen Again ERROR Fixed Again dormant FOLDER Fixed DROP ERROR Drop can FOR happen FOR 3 folder Even Child correct Current Create CREATED Again button Again FIX from first From ERROR folder first Drag Again first Detail from Fixed dormant Duplicate folder Detail DORMANT FOR Again DORMANT FOLDER Again Fixed FOLDER From Again FIX Detail ERROR Fixed From Detail ERROR Fixed Again FOLDER does Even Drag dormant From Again ERROR Fixed DORMANT Drag folder Drag Fixed DORMANT Drag Fixed dormant Drag Again Detail first first FOLDER GET ERROR Fixed Drop Again first ERROR even Drag Again FOLDER does Even Drag dormant From FOR Again DROP following FOLDER FIX Again FOLDER Fixed Drag Again folder Detail DORMANT Again From FOLDER Again Drop Drag From Again DORMANT Drag first Drag From Drag DORMANT Again DROP following FOLDER FIX Again Detail Fixed FOLDER From Duplicate Drag following method 300 folder Even Child correct Current CREATED click Again button Again DROP DORMANT ERROR FOR even Again ERROR Fixed DORMANT ERROR dormant Detail From Drag FOR Again Detail Again dormant FOLDER following following from folder From Drag DORMANT Again Duplicate Detail following DORMANT ERROR FOR even Again ERROR DROP Again From Duplicate Drag following Drag Again Detail following Drag Again Detail ERROR had Again folder Detail following From ERROR From ERROR FOLDER Fixed FOR Again FOLDER Fixed Again From Duplicate Drag Again FOR Drag dormant FOLDER Fixed DORMANT Again Duplicate Detail following DORMANT following ERROR get Drag be GET Detail following folder because 4 folder Even Child correct Current created Changed Again button Again From following Detail folder Again Changed Changed Changed Drag Again GET Duplicate Drag Fixed Again ERROR Fixed FOR From Detail first first ERROR Fixed Drop Again folder Drag following FOR FOLDER Fixed button From FOLDER button folder Drag following FOR FOLDER Fixed Again be folder click folder because Again FOLDER Fixed Again Detail Fixed Again ERROR does FIX Again Again From Duplicate ERROR Fixed even folder Detail DORMANT Again CREATED click Changed Again GET ERROR From Duplicate Again folder dormant FIX dormant ERROR Detail Again FIX FOLDER DORMANT Drag FIX Again ERROR Fixed FOR From Detail first first Drag DORMANT can 5 folder Even Child correct Current created created Again button Again DROP DORMANT ERROR FOR even folder FIX Again from From ERROR first ERROR From happen Again be GET Detail following folder because Again DROP Detail ERROR first FOR Again GET Duplicate Drag Fixed Again From following happen ERROR Fixed Drop Again From FOLDER Again DORMANT Drag first Drag From Drag Again first FOLDER Drop ERROR dormant Detail first Again folder Detail following From Again Again From ERROR FOLDER Fixed FOR Again FIX Detail FOR From Drag following Again does FOLDER FOLDER From Again following Drag dormant FOLDER following DORMANT Again does Drag dormant FOLDER FIX Drag FOR Again dormant FOLDER following following from folder From behavior Again FOR happen FOR From Drag FIX Again DROP Detail ERROR first FOR Again From FOLDER Again does FOLDER FOLDER From get 562260100 folder Even Child correct Current Current correct Again button Again FOR Drag first Drag dormant From ERROR get Drag Again ERROR Fixed FOR From Detail first first Again ERROR Fixed Again GET Detail following folder Again following Drag FOR from first From Again ERROR Fixed Again FOR happen FOR Closed Child CREATED correct Again ERROR Fixed Again Again FOLDER FOR click FIX FIX can DORMANT first first Again Changed Changed Changed Child Date Changed Changed Changed click Current Closed Changed dormant 6 folder Even Child correct Current Current CREATED Again button Again Fixed FOLDER Again FOLDER folder From ERROR FOLDER Fixed Again From FOLDER Again following Drag FOR ERROR HAVE Drag Again Detail get ERROR Again GET ERROR Fixed DORMANT FOLDER GET Again from FOR ERROR Fixed Drop Again Detail Fixed Again ERROR does FIX Again created correct Child Component cannot Detail Again get ERROR DORMANT Drag FOLDER Again dormant Detail following DORMANT can Again From Drag FOR From Drag DORMANT Again created correct Child Component Again FIX FOLDER DORMANT Drag Again be Child Changed click Component had CREATED Create created had click correct Create because Again Detail Fixed DORMANT Again get Drop Detail Again GET ERROR From Duplicate Again From Duplicate Drag Again FOR Detail FIX Drag Again following Drag FOR from first From FOR can 94 folder Even Child Create Changed Changed Changed Again button Again From Duplicate Drag Again GET Detail following folder Again Detail from From FOLDER button FIX ERROR Drop following Detail From Drag Again DROP Drag Detail From from following Drag Again ERROR FOR Again Drag following following FOLDER Fixed Drag FOLDER from FOR first happen Again FOR Drag first Drag dormant From ERROR Fixed Drop Again and ERROR does FIX Again dormant Again cannot FOR Drag From Again click Again FOLDER Fixed first ERROR Fixed Drag Again Duplicate Drag first folder and Again Again DROP FOLDER following Again Detail Fixed happen Again dormant Date if FOLDER FOR click if get ERROR Drag GET can Drag had Drag Again folder Detail From Duplicate can LOCAL : A folder Even Child Create Changed Child Current Again button Again Drag had dormant Drag folder From ERROR FOLDER Fixed Again ERROR Fixed Again FOR ERROR Fixed Drop first Drag follow arrow Again FOLDER FOR click Again get Closed can Changed be GET Detail following folder because Again first FOLDER Detail DORMANT ERROR Fixed Drop Again FOR get Drop Detail Again DORMANT following ERROR get Drag following can Again Drag ERROR folder Again get Detail first from Drag Again FOR Duplicate FOLDER from first DORMANT Again does Drag Again Changed Changed Changed Changed Changed Current CREATED Child can Detail a able folder Even Child Create Changed click Changed Again button Again FOR happen FOR Closed Child CREATED correct Again Detail From Again Child CREATED DROP DROP Component Detail CREATED Closed Again ERROR Fixed Again does get Duplicate FOR get Drop Detail can DORMANT first first Again GET Detail following folder Again had following Changed Closed Changed Changed Changed can ERROR AFTER folder Even Child Create Changed click click Again button Again had following Changed Closed Changed Changed Changed Again created Changed Changed had Create Changed Changed had Create Component even Again dormant FOLDER following following from folder From ERROR FOLDER Fixed Again ERROR Fixed Again DORMANT FOLDER FOR Again Detail Fixed DORMANT Again FOLDER FOR click Again DROP from first first Again FOR dormant following Drag Drag Fixed can dormant after folder Even Child Create Changed Closed Create Again button Again Drop following Drag Detail From Again folder first Detail ERROR Fixed FOR Again DORMANT happen Fixed Detail FIX ERROR dormant FOR Again be Detail dormant dormant FOLDER from Fixed From ERROR Fixed Drop because Again Drop Drag From Again GET ERROR Fixed Closed click FOR Again Drag following following FOLDER following can Again folder Even Child Create Changed Closed Current Again button Again FOR Duplicate ERROR DROP From been DROP Child Changed Again DROP Detail ERROR first FOR Again From FOLDER Again DORMANT ERROR FOR folder first Detail happen Again FOLDER does Even Drag dormant From Available FOR Again dormant FOLDER Fixed From Drag had From Again FIX Drag Fixed from Again DROP following FOLDER FIX Again first Detail from Fixed dormant Duplicate folder Detail DORMANT Again DORMANT ERROR FOR folder first Detail happen ERROR Fixed Drop Again first Detail from Fixed dormant Duplicate folder Detail DORMANT Available FOR Again dormant FOLDER Fixed From Drag had From Again FIX Drag Fixed from Again ERROR Fixed FOR From Drag Detail DORMANT AND folder Even Child Create Changed Component Changed Again button Again FIX FOLDER get Drag Again FOLDER DROP Again FOLDER does Even Drag dormant From Again DROP following FOLDER FIX Again first Detail from Fixed dormant Duplicate folder Detail DORMANT Again get ERROR Detail Again FOLDER does Even Drag dormant From Available FOR Again dormant FOLDER Fixed From Drag had From Again FIX Drag Fixed from Again first Drag Detail get Drag FOR Again Detail Again from Fixed from FOR Detail does first Drag Again FOLDER does Even Drag dormant From Again FOLDER Fixed Again From Duplicate Drag Again folder Detail DORMANT Again From Duplicate Detail From Again GET ERROR first first Again Detail first FOR FOLDER Again does Drag dormant FOLDER FIX Drag Again DORMANT ERROR FOR dormant FOLDER Fixed Fixed Drag dormant From Drag DORMANT and folder Even Child Create Changed Component Closed Again button Again From Duplicate Drag Again Fixed Detail FIX Drag Again FOLDER FIX Fixed ERROR can FOLDER even ERROR DORMANT Detail From Detail Again had had had Again ERROR FOR Again FIX ERROR FOR first Drag Detail DORMANT ERROR Fixed Drop can Again From Duplicate ERROR FOR Again DORMANT following ERROR get Drag following Again from FOR Drag FOR Again From Duplicate Drag Again Drag folder FOR FOLDER Fixed Again first Detail Fixed Drop from Detail Drop Drag Again Detail Fixed DORMANT Again Fixed FOLDER From Again Detail Fixed Again FOLDER even ERROR DORMANT Detail From Detail Again first Detail Fixed Drop from Detail Drop Drag can Detail APAR folder Even Child Create Changed Component Current Again button Again From following Detail folder Again Drag Again GET Duplicate Drag Fixed Again following from Fixed Fixed ERROR Fixed Drop Again DORMANT Detail From Detail Drop first Detail Fixed dormant Drag Again get Again Child can click Child Again FOLDER Fixed Again FOLDER FOR cannot click Again GET Detail following folder FOLDER arrow folder Even Child Create Changed correct Closed Again button Again FOR happen FOR Closed Child CREATED correct Again GET Duplicate Drag Fixed Again ERROR Fixed FOR From Detail first first ERROR Fixed Drop Again FOLDER FOR cannot click Again GET Detail following folder Again FOLDER Fixed Again Detail Fixed Again Detail FIX does following Detail Again FOR first ERROR FIX first ERROR Fixed Drag Again created Changed Component created Create FOR first dormant click following as folder Even Child Create Changed correct created Again button Again FOR FOLDER Fixed happen Again correct correct Drag Again Detail Fixed DORMANT Again correct correct DORMANT behavior Again FIX ERROR From FOR from FIX ERROR Again DROP had Changed Changed Child DORMANT Drag Again dormant DORMANT following FOLDER FIX Available FOR Again DORMANT FOLDER Again Fixed FOLDER From Again GET FOLDER following even Again ERROR Fixed Again GET Detail following folder can Again first Child FOLDER even Last At folder Even Child Create Changed Create Component Again button Again click created created Changed Changed cannot FIX Detail dormant Duplicate created Again DORMANT following ERROR get Drag following FOR Again GET ERROR first first Again Fixed FOLDER From Again ERROR Fixed FOR From Detail first first Again FOLDER Fixed Again FOR happen FOR From Drag FIX FOR Again GET ERROR From Duplicate Again From Duplicate Drag Again Drop following Detail folder Duplicate ERROR dormant FOR Again from first From following Detail Again be GET ERROR From Duplicate Again Detail Again FIX Detail dormant Duplicate created because just Available folder Even Child Create Changed CREATED Changed Again button Again GET ERROR Fixed FOLDER FOR cannot click Again FOR Drag Detail FIX first Drag FOR FOR Again Detail folder folder first ERROR dormant Detail From ERROR FOLDER Fixed Again Drag following following FOLDER following Again GET Duplicate Drag Fixed Again following from Fixed Fixed ERROR Fixed Drop Again Detail folder folder first ERROR dormant Detail From ERROR FOLDER Fixed Again GET ERROR From Duplicate Again Again From Duplicate Drag Again FIX Detail dormant Duplicate Closed click Again DORMANT following ERROR get Drag following FOR does be folder Even Child Create Changed CREATED Component Again button Again Detail DORMANT Detail folder From Drag dormant Again Child Create Component Changed Again FIX dormant Detail Again dormant Detail following DORMANT Again from Fixed DORMANT Drag following Again GET Detail following folder Again DROP Detail ERROR first FOR Again From FOLDER Again FOR Drag Drag Again dormant DORMANT following FOLDER FIX DROP because folder Even Child Create Changed CREATED correct Again button Again Detail folder FIX can FOR happen FOR Again Fixed FOLDER From Again FIX ERROR Drop following Detail From Drag DORMANT Again folder following FOLDER folder Drag following first happen Again DORMANT from following ERROR Fixed Drop Again GET Detail following folder Again ERROR Fixed FOR From Detail first first Detail From ERROR FOLDER Fixed can BEEN been behavior folder Even Child Create Changed CREATED CREATED Again button Again FOR happen FOR From Drag FIX Again Duplicate Detail Fixed Drop FOR Again FOLDER Fixed Again GET Detail following folder Again DORMANT ERROR FOR even Child Again GET ERROR From Duplicate Again Detail Again does first Detail Fixed even Again FOR dormant following Drag Drag Fixed behavior Again dormant from following FOR FOLDER following Again does first ERROR Fixed even ERROR Fixed Drop Again ERROR Fixed Again From FOLDER folder Again first Drag DROP From can Again ERROR does FIX even does DORMANT can FOR happen FOR Again does following FOLDER even Drag Fixed cannot following Drag Drop following Drag FOR FOR Drag DORMANT can does button can folder Even Child Create Changed created Child Again button Again Drag Detail FOR happen GET following ERROR From Drag following Again click can Changed Again Drag following following FOLDER following Again dormant Detail Fixed Available From Again following Drag Detail DORMANT Again DORMANT following ERROR get Drag Again following Again be dormant FOLDER DORMANT Drag Again Child click because cannot Changed folder Even Child Create Changed created correct Again button Again from Fixed HAVE ERROR folder Again folder following FOLDER does first Drag FIX Again ERROR Fixed FOR From Detail first first ERROR Fixed Drop Again and ERROR Fixed From Drag following Fixed Drag From Again dormant FOLDER Fixed Fixed Drag dormant From ERROR FOLDER Fixed Again DROP FOLDER following Again FOLDER FOR cannot click and Again folder FOLDER following From ERROR FOLDER Fixed Again FOLDER DROP Again From Duplicate Drag Again GET Detail following folder Again does FOLDER Fixed from FOR folder Detail dormant even Again DROP following FOLDER FIX Again dormant DORMANT following FOLDER FIX Again FOLDER Fixed Again FIX ERROR From FOR from FIX ERROR Again DORMANT following ERROR get Drag FOR can from Child folder Even Child Create Changed created Create Again button Again GET Detail following folder Again ERROR Fixed FOR From Detail first first Detail From ERROR FOLDER Fixed Again Duplicate Detail Fixed Drop FOR Again FOLDER Fixed Again DORMANT ERROR FOR even APAR Child Again GET ERROR From Duplicate Again folder FOLDER GET Drag following Drop following Detail folder Duplicate Again get first button click Component Again FOR From does Again get ERROR DORMANT Drag FOLDER Again dormant Detail following DORMANT Identifier click folder Even Child Create Changed created Current Again button Again FIX Detail dormant Duplicate Closed click Again DORMANT following ERROR get Drag following Again Duplicate Detail Fixed Drop FOR Again FOR happen FOR From Drag FIX Again GET Duplicate Drag Fixed Again FOR GET ERROR From dormant Duplicate ERROR Fixed Drop Again DROP following FOLDER FIX Again DORMANT Drag FOR even From FOLDER folder Again From FOLDER Again GET ERROR Fixed FOLDER FOR cannot click Again DROP from first first FOR dormant following Drag Drag Fixed Drop Closed folder Even Child Create Changed Current Changed Again button Again DORMANT FOLDER FOR cannot GET ERROR Fixed DORMANT FOLDER GET FOR Again FOR Drag Detail FIX first Drag FOR FOR Again dormant FOLDER following following from folder From Again from FOR ERROR Fixed Drop Again FOR Closed Again DORMANT following ERROR get Drag following FOR Again from Fixed DORMANT Drag following Again GET Detail following folder HAVE Component folder Even Child Create Changed Current click Again button Again GET Detail following folder Again first Drag get Drag first Again ERROR does FIX FOR Child correct Changed Create Again DORMANT following ERROR get Drag following Again GET ERROR first first Again Fixed FOLDER From Again GET FOLDER following even Again GET ERROR From Duplicate Again dormant FOLDER Fixed Fixed Drag following Again dormant folder Closed click Changed Component DROP Again DORMANT following ERROR get Drag Again Detail FOR Again FOR first Detail get Drag DROP correct folder Even Child Create Changed Current Closed Again button Again follow from ERROR dormant even does FOLDER FOLDER even FOR Again FOLDER folder Drag Fixed Again DROP ERROR first Drag Again DORMANT ERROR Detail first FOLDER Drop Again does FOLDER had Again FOLDER folder Drag Fixed FOR Again ERROR Fixed Again From Duplicate Drag Again does Detail dormant even Drop following FOLDER from Fixed DORMANT Even Create CREATED folder Even Child Create Changed Current Component Again button Again GET FOLDER following DORMANT Again folder Drag following DROP Drag dormant From Again FOLDER DROP DROP ERROR dormant Drag cannot Fixed FOLDER get Drag first first Again Drop following FOLDER from folder GET ERROR FOR Drag Again created click Changed Drag Again DROP ERROR first Drag Again ERROR cannot FOLDER Again Drag following following FOLDER following can created folder Even Child Create Changed Current correct Again button Again dormant FOLDER FIX can FOR happen FOR Again Fixed FOLDER From Again GET FOLDER following even ERROR Fixed Drop Again FOLDER Fixed Again Drag ERROR FOR Detail Again FIX Detail dormant Duplicate ERROR Fixed Drag FOR can Again Again FOR happen FIX folder From FOLDER FIX FOR Again Detail following Drag Again Duplicate Detail Fixed Drop FOR Again FOLDER following Again Detail Again FIX Drag FOR FOR Detail Drop Drag Again ERROR Fixed DORMANT ERROR dormant Detail From ERROR Fixed Drop Again dormant FOLDER FIX Again folder FOLDER following From Again Fixed FOLDER From Again ERROR Fixed FOR From Detail first first Drag DORMANT can Again Again first Child FOLDER even is Current Date folder Even Child Create Changed Current Create Again button Again and following Drag Detail first Again GET FOLDER following first DORMANT Again folder following FOLDER Drop following Detail FIX FIX ERROR Fixed Drop Again DROP FOLDER following Again FOLDER FOR cannot click Again click can Child and Again DORMANT ERROR FOR even Drag From From Drag Again Duplicate Detail Fixed Drop FOR Again GET Duplicate Drag Fixed Again ERROR Fixed FOR From Detail first Again first Drag DORMANT Again FOLDER Fixed Again GET Detail following folder Again Closed had Delete folder Even Child Create Child Changed Component Again button Again GET Detail following folder Again ERROR Fixed FOR From Detail first first Detail From ERROR FOLDER Fixed Again DROP Detail ERROR first FOR Again FOLDER Fixed Again DORMANT ERROR FOR even Drag From From Drag APAR click Again GET ERROR From Duplicate Again FOR happen FOR Changed Changed Closed CREATED Again DROP FOLDER first first FOLDER GET Drag DORMANT Again does happen Again From following Detail folder Again Changed Changed Changed DORMANT can just delete folder Even Child Create Child Changed correct Again button Again From following Detail folder Again Changed Changed Closed Again ERROR Fixed Again FIX Detail dormant Duplicate ERROR Fixed Drag FOR Again GET ERROR From Duplicate Again ERROR DORMANT Drag Again dormant DORMANT following FOLDER FIX Again GET ERROR From Duplicate Again Duplicate Drag Detail get happen Again FOR GET Detail folder folder ERROR Fixed Drop Again Again from Fixed DORMANT Drag following Again GET Detail following folder Again FOLDER FOR cannot click Again get Drag following FOR ERROR FOLDER Fixed Again Closed can Changed NOT deleted folder Even Child Create Child Changed Create Again button Again GET ERROR first DORMANT dormant Detail From Again does does FOR Again Again Component can Changed Again At Again Component can Child Again GET Duplicate Drag Fixed Again FOR Drag From Again From FOLDER Again DORMANT FOLDER FOR Again FOR Duplicate Detail following Drag Again ERROR FOR Again Drop ERROR get ERROR Fixed Drop Again Drag following following FOLDER following Again Date Again and from Fixed Detail does first Drag Again From FOLDER Again ERROR Fixed ERROR From ERROR Detail first ERROR HAVE Drag Again Fixed Drag From GET FOLDER following even Again Child Changed Closed Child Changed and Even DELETED folder Even Child Create Child Changed CREATED Again button Again From following Detail folder Again Changed Changed Changed created Again GET ERROR From Duplicate Again FOR FOR Again deleted Again Changed Changed Drag created Again FOLDER following Again Changed Changed Current Changed Again Detail Fixed DORMANT Again Drag FOR folder Again first Drag FOR FOR Again From Duplicate Detail Fixed Again Detail does FOLDER from From Again Child Changed following DESCRIPTION folder Even Child Create Child Changed created Again button Again get ERROR FOLDER Again folder following FOLDER Drop following Detail FIX Again FOR From Detail following From Drag DORMANT Again GET ERROR From Duplicate Again From ERROR From first Drag Again FOR folder Drag dormant ERROR DROP ERROR Drag DORMANT Again Duplicate Detail FOR Again DORMANT Drag DROP Detail from first From Again FIX ERROR Fixed ERROR FIX ERROR HAVE Drag DORMANT Again ERROR dormant FOLDER Fixed Desktop folder Even Child Create Child Child Changed Again button Again from FIX cannot click Again first ERROR From Drag Again ERROR Fixed dormant FOLDER following following Drag dormant From first happen Again Detail FOR FOR from FIX Drag FOR Again ERROR Detail even Again from FOR Drag following button ERROR DORMANT Again ERROR Fixed FOR From Drag Detail DORMANT Again FOLDER DROP Again folder FOLDER folder Again from FOR Drag following Again ERROR DORMANT Again Detail FOR Again Drag Fixed From Drag following Drag DORMANT Again ERROR Fixed Again and from FOR Drag Again Detail Fixed FOLDER From Duplicate Drag following Again ERROR Fixed From Drag following Fixed Drag From Again folder following FOLDER get ERROR DORMANT Drag following and Again DORMANT ERROR Detail first FOLDER Drop from Drag FOR Fixed Detail folder Even Child Create Child Child click Again button Again FOR get Drop Detail can Drag had Drag Again DORMANT FOLDER Drag FOR Again Fixed FOLDER From Again following Drag dormant FOLDER Drop Fixed ERROR HAVE Drag Again From Duplicate Drag Again FIX Detail dormant Duplicate Closed click Again FOLDER Fixed Again Detail Again FIX ERROR dormant following FOLDER dormant Duplicate Detail Fixed Drag first Again FIX Detail dormant Duplicate ERROR Fixed Drag does folder Even Child Create Child Child Closed Again button Again GET ERROR From Duplicate Again From Duplicate Drag Again first Detail From Drag FOR From Again get Drag following FOR ERROR FOLDER Fixed Again FOLDER DROP Again FOLDER FOR cannot click Again be GET Detail following folder because behavior Again GET Duplicate Drag Fixed Again from FOR ERROR Fixed Drop Again From Duplicate Drag Again Detail DORMANT FOR FIX Again does cannot Detail Again Drop from ERROR behavior Again From Duplicate Drag following Drag Again ERROR FOR Again Detail Again folder following FOLDER does first Drag FIX Again GET ERROR From Duplicate Again From Duplicate Drag Again folder Detail FOR FOR GET FOLDER following DORMANT Again does Drag ERROR Fixed Drop Again even Fixed FOLDER GET Fixed can dormant folder Even Child Create Child Child correct Again button Again ERROR dormant FOLDER Fixed Again DORMANT ERROR FOR folder first Detail happen Again FOR FIX Detail first first Again FOR ERROR HAVE Drag Again Detail Fixed DORMANT Again Detail first GET Detail happen FOR Again FIX Detail ERROR Fixed From Detail ERROR Fixed Again FOR FOLDER following From Again FOLDER following DORMANT Drag following Again Detail following Drag Again Fixed FOLDER From Again even Drag folder From Again DROP FOLDER following Again Fixed Drag From GET FOLDER following even Again DORMANT following ERROR get Drag Again FOR Drag From From ERROR Fixed Drop FOR Again from Fixed DORMANT Drag following Again FOLDER FOR cannot click Again GET Detail following folder Again Detail DROP From Drag following Again following Drag does FOLDER FOLDER From mouse DORMANT folder Even Child Create Child Child Create Again button Again ERROR dormant FOLDER Fixed FOR Again FOLDER DROP Again FOR Drag Detail FIX first Drag FOR FOR Again GET ERROR Fixed Detail folder FOR Again be first FOLDER dormant Detail first first happen because Again Detail following Drag Again Fixed FOLDER From Again dormant following FOLDER FOR FOR Again Duplicate Detail From dormant Duplicate ERROR Fixed Drop Again GET Duplicate Drag Fixed Again From Duplicate Drag happen Again Detail following Drag Again following from Fixed Again DROP FOLDER following Again From Duplicate Drag Again Child FOR From Again From ERROR FIX Drag can DELETED Drag folder Even Child Create Child click Child Again button Again GET Detail following folder Again Detail Duplicate Detail Child correct click had can Detail DORMANT DORMANT Again Fixed FOLDER From Again GET FOLDER following even ERROR Fixed Drop Again GET ERROR From Duplicate Again FOR FOLDER FIX Drag Again dormant DORMANT following FOLDER FIX Available FOR can DROP folder Even Child Create Child click click Again button Again FOR happen FOR Closed Child CREATED Changed Again GET Duplicate Drag Fixed Again dormant first FOLDER FOR ERROR Fixed Drop Again ERROR does FIX Again GET FOLDER following even FOR behavior Again DROP Detail had GET FOLDER following even FOR Again FOLDER following Again Detail FIX ERROR folder following FOLDER Again DROP FOLDER following Again FOLDER FOR cannot click Again Drag had dormant Drag folder From ERROR FOLDER Fixed Again dormant Changed Changed Child Changed Changed Changed Child Again Detail From Again Child does DROP Detail does DROP correct Child Again Again Again dormant FOR Date Drag ERROR folder Again Changed Changed correct does Date Child does DORMANT Component Current DROP created DORMANT LOCAL Drop folder Even Child Create Child click Closed Again button Again and DROP first FOLDER Detail From Again From FOLDER Again From FOLDER folder and Again FOLDER folder From ERROR FOLDER Fixed Again FOR From ERROR first first Again dormant Detail from FOR ERROR Fixed Drop Again From following Detail folder FOR Again ERROR Fixed Again FOR happen FOR From Drag FIX Again Drag DORMANT ERROR From FOLDER following Again GET Duplicate Drag Fixed Again FOR Detail get ERROR Fixed Drop Again DROP ERROR first Drag FOR Again GET ERROR From Duplicate Again Fixed FOLDER Again Drag Detail Available FOR Duplicate folder Even Child Create Child click Component Again button Again FIX Drag FOR FOR Detail Drop Drag Again and Again FIX ERROR Drop following Detail From Drag Again happen FOLDER from following Again Drag had ERROR FOR From ERROR Fixed Drop Again dormant FOLDER Fixed DROP ERROR Drop from following Detail From ERROR FOLDER Fixed Again DROP ERROR first Drag FOR Again GET ERROR From Duplicate Again happen FOLDER from following Again Fixed Drag Again GET Again dormant FOLDER Fixed DROP ERROR Drop from following Detail From ERROR FOLDER Fixed Again DROP ERROR first Drag FOR Again and Again ERROR FOR Again dormant FOLDER Fixed DROP from FOR ERROR Fixed Drop can follow ERROR folder Even Child Create Child click correct Again button Again GET Detail following folder Again dormant DORMANT following FOLDER FIX Again DORMANT following ERROR get Drag following Again FOR does dormant DORMANT click can Detail DORMANT DORMANT Again DORMANT FOLDER Drag FOR Again Fixed FOLDER From Again GET FOLDER following even Again GET ERROR From Duplicate Again following Drag get Drag Detail first Again dormant DORMANT following FOLDER FIX can Again Again first Child FOLDER even if Even folder Even Child Create Child click Create Again button Again does first Detail dormant even Again FOR dormant following Drag Drag Fixed Again GET Duplicate Drag Fixed Again FOR From Detail following From ERROR Fixed Drop Again from Fixed DORMANT Drag following Again Detail Again even ERROR first first ERROR Fixed Drop Again FIX FOLDER FOLDER Fixed Again ERROR Fixed Again Detail Again DORMANT FOLDER FOR Again DROP from first first Again FOR dormant following Drag Drag Fixed Again FOR Drag FOR FOR ERROR FOLDER Fixed can new even folder Even Child Create Child click CREATED Again button Again Duplicate Drag first folder Again FIX Detail Fixed Detail Drop Drag following Available FOR Again FOR Drag Detail following dormant Duplicate Again DROP from Fixed dormant From ERROR FOLDER Fixed Again GET ERROR first first Again DROP Detail ERROR first Again ERROR DROP Again From Duplicate Drag Again ERROR Fixed DROP Again does Drag ERROR Fixed Drop Again get ERROR Drag GET Drag DORMANT Again Duplicate Detail FOR Again FIX FOLDER following Drag Again From Duplicate Detail Fixed Again Closed click CREATED Create CREATED Again from Fixed ERROR follow from Drag Again GET FOLDER following DORMANT FOR can first folder Even Child Create Child click Current Again button Again ERROR Fixed Again Detail Again FOR Drag Detail FIX first Drag FOR FOR Again FOR Drag FOR FOR ERROR FOLDER Fixed Again Detail DROP From Drag following Again ERROR Fixed From ERROR Detail first Again FOR FOLDER from Fixed DORMANT Again Duplicate Detail FOR Again does Drag Drag Fixed Again folder following FOLDER DORMANT from dormant Drag DORMANT Again Fixed FOLDER Again FOLDER Again Again Duplicate Drag following Again GET Detail get Drag Again DROP ERROR first Drag Again dormant Detail Fixed Again does Drag Again folder first Detail happen Drag DORMANT can Again Again FOR FOLDER from Fixed DORMANT Again ERROR Fixed Again FOR Drag Detail FIX first Drag FOR FOR Even FIX folder Even Child Create Child Closed Changed Again button Again Child click created Changed had Child Changed click Component had click correct Create Again GET following Detail folder FOR Again Detail following FOLDER from Fixed DORMANT Again FOR dormant following Drag Drag Fixed Again from FOR ERROR Fixed Drop Again FOR Closed Again DORMANT following ERROR get Drag following FOR Again ERROR Fixed Again GET Detail following folder can Fixed folder Even Child Create Child Closed Child Again button Again dormant Duplicate Detail Fixed Drop ERROR Fixed Drop Again Detail following dormant Duplicate ERROR get Drag Again first FOLDER dormant Detail From ERROR FOLDER Fixed Again DORMANT FOLDER Drag FOR Again Fixed FOLDER From Again GET FOLDER following even Again from Fixed DORMANT Drag following Again FOLDER FOR cannot click Again GET Detail following folder Date Again FOR happen FOR From Drag FIX Again GET ERROR first first Again FOLDER Fixed first happen Again does FOLDER FOLDER From Again From FOLDER Again folder FIX Again GET ERROR From Duplicate Again Fixed FOLDER Again DORMANT Drag FOR even From FOLDER folder NOT FOLDER folder Even Child Create Child Closed click Again button Again following from Fixed ERROR Fixed Drop Again first FOLDER From from DORMANT Again Child click Closed Again get Drag following Again click can click Again DROP FOLDER following Again DORMANT FOLDER FOR Again ERROR Fixed Again DORMANT FOLDER FOR Again DROP from first first Again FOR dormant following Drag Drag Fixed Again does following Drag Detail even FOR Again From Duplicate Drag Again first ERROR Fixed Drag Again ERROR Fixed Again Detail Fixed happen Again dormant Duplicate Detail following Detail dormant From FOLDER following Again does Detail FOR Drag DORMANT Again FOR Drag FOR FOR ERROR FOLDER Fixed can folder folder Even Child Create Child Closed Closed Again button Again Detail DROP From Drag following Again From following Detail folder folder ERROR Fixed Drop Again Detail Fixed DORMANT Again From following happen ERROR Fixed Drop Again From FOLDER Again following from Fixed Again Detail Again folder following ERROR Fixed From FOR dormant following Drag Drag Fixed Again FOLDER Fixed Again Detail Again FOR happen FOR From Drag FIX Again From Duplicate Detail From Again DORMANT FOLDER Drag FOR Again Fixed FOLDER From Again Duplicate Detail get Drag Again Detail Again folder following ERROR Fixed From Drag following Again Detail From From Detail dormant Duplicate Drag DORMANT Again FOR happen FOR From Drag FIX Again GET ERROR first first Again Duplicate Detail Fixed Drop follow folder Even Child Create Child Closed Component Again button Again DORMANT FOLDER following FIX Detail Fixed From Again FOR Duplicate Detail DORMANT FOLDER GET Again FOLDER DROP Again DORMANT Drag first Drag From Drag DORMANT Again DROP FOLDER first DORMANT Drag following Again Drop Drag From Again dormant following Drag Detail From Drag DORMANT Again Detail DROP From Drag following Again folder ERROR dormant even from folder Again Detail Fixed DORMANT Again DORMANT following FOLDER folder Again FOLDER following Again Detail Again FOR Duplicate Detail DORMANT FOLDER GET behavior Again DROP FOLDER following Again DROP FOLDER first DORMANT Drag following Again From Duplicate Detail From Again Fixed Drag get Drag following Again FOR Duplicate FOLDER from first DORMANT Again Duplicate Detail get Drag Again does Drag Drag Fixed Again DORMANT Drag first Drag From Drag DORMANT HAVE following folder Even Child Create Child Component Component Again button Again from FOR ERROR Fixed Drop Again GET Detail following folder Again FOR Closed Again DORMANT following ERROR get Drag following FOR Again ERROR Fixed Again Child click created Changed had Child Changed click Component Again following Drag FOR FOLDER first from From ERROR FOLDER Fixed Again Duplicate Detail Fixed Drop FOR Again DORMANT FOLDER FOR Again DROP from first first FOR dormant following Drag Drag Fixed Again FOR Drag FOR FOR ERROR FOLDER Fixed can list FOR folder Even Child Create Child Component created Again button Again from Fixed DORMANT Drag following Again GET Detail following folder behavior Again DORMANT FOLDER FOR follow from Drag following happen dormant from following following Drag Fixed From DORMANT ERROR following Again Detail Fixed DORMANT Again FOLDER From Duplicate Drag following Again Detail folder ERROR FOR Again Fixed Drag Drag DORMANT first Drag FOR FOR first happen Again following Drag From from following Fixed Again Drag following following FOLDER following is ERROR Fixed get Detail first ERROR DORMANT is folder Detail following Detail FIX Drag From Drag following even From folder Even Child Create Child Component Current Again button Again folder dormant FIX dormant ERROR Detail Again DORMANT following ERROR get Drag following FOR Again Fixed FOLDER From Again ERROR Fixed FOR From Detail first first Drag DORMANT Again dormant FOLDER following following Drag dormant From first happen Again DROP FOLDER following Again FOLDER FOR click Again GET Detail following folder Again GET ERROR From Duplicate Again dormant ERROR DORMANT method from folder Even Child Create Child correct Changed Again button Again GET DORMANT Again Current Changed dormant Closed Closed Again dormant Duplicate ERROR folder FOR Drag From Again Duplicate Detail Fixed Drop FOR Again From Duplicate Drag Again FOR happen FOR From Drag FIX Again FOLDER Fixed Again DORMANT ERROR FOR folder first Detail happen Again DORMANT following ERROR get Drag following Again DORMANT ERROR FOR even Drag From From Drag Again FOLDER following Again following Drag FOR from first From Again ERROR Fixed Again get ERROR DORMANT Drag FOLDER Again dormant FOLDER following following from folder From ERROR FOLDER Fixed FOR can get folder Even Child Create Child correct Child Again button Again ERROR does FIX click FOR dormant FOR ERROR Again GET FOLDER Fixed Available From Again Detail first first FOLDER GET Again does FOLDER FOLDER From Again folder Detail following From ERROR From ERROR FOLDER Fixed FOR Again DELETED Again Component Again Drop ERROR Drop FOR Again FOLDER following Again does Drag happen FOLDER Fixed DORMANT Again Component Again Drop ERROR Drop FOR Again ERROR DROP Again From Duplicate Drag Again folder Detail following From ERROR From ERROR FOLDER Fixed FOR Again Detail following Drag Again FOR FIX Detail first first Again from Fixed DORMANT Drag following Again FOLDER FOR click Again Closed can Changed behavior Again click can Child Child Again Detail does DORMANT Again does Drag first FOLDER GET GET folder Even Child Create Child correct click Again button Again Detail DROP From Drag following Again Detail Fixed Again Detail folder folder Detail following Drag Fixed From first happen Again FOR from dormant dormant dormant Drag FOR FOR DROP from first Again ERROR Fixed FOR From Detail first first behavior Again FIX Deta