Warp Tips: Difference between revisions

From OS2World.Com Wiki
Jump to navigation Jump to search
No edit summary
 
(61 intermediate revisions by 2 users not shown)
Line 1: Line 1:
by [[Irv Spalten]]
{{Article
|Author=[[Irv Spalten]]
|Date=1994-12-12
|OS=OS/2 Warp 3
|File=N/A
|Source=
}}
Information current as of December 12, 1994


Information current as of December 12, 1994
These are solutions to problems encountered in OS/2 Warp.


These are solutions to problems encountered in OS/2 Warp.
==941026 THE SWAPPER FILE IN WARP==
DESCRIPTION OF SYMPTOMS:


==TITLE: 941027 INSTALLATION OF WARP HANG ON DISK #1 WHEN INSTALL ON GATEWAY COMPUTERS.==
The swapper file is larger in WARP than in previous releases of OS2.
 
SUMMARY OF RESOLUTION:
 
This is normal.
   
   
DESCRIPTION OF SYMPTOMS:
DETAILS OF RESOLUTION:
     Hang on DISK #1 when installing WARP on Gateway machines.
 
This is normal.
The most significant change that has been made is how system DLL's get loaded and what is now valid data for swapping.
System DLL's include:
     DISPLAY          SOM          PMMERGE      PMWP
    DOSCALL1        PMATM        PMMLE
    IBMDEV32        PMCTLS      PMSPL
    IBMVGA32        PMGPI        PMVIOP
   
   
RESOLUTION:
In the previous versions of OS/2, dll code was never copied to the
    If you are having this problem, please check  
swapper file. In WARP, code for system dll's can be written to
    the level of BIOS on your system. If you have  
the swapper file and, in adition, during boot, PMMERGE, DOSCALL1,
    a Gateway 1.00.03.AF1 BIOS, then you need to  
PMGPI, PMWP and PMVIOP will be swapped out. This means that there
    update your BIOS (see the README).
will be an overall increase in swapper size. This was done
    A fix is available from Gateway.
to increase overall system perfomance.
 
==941027 INSTALLATION OF WARP HANG ON DISK #1 WHEN INSTALL ON GATEWAY COMPUTERS==
;DESCRIPTION OF SYMPTOMS:
Hang on DISK #1 when installing WARP on Gateway machines.
 
;RESOLUTION:
If you are having this problem, please check the level of BIOS on your system. If you have  
a Gateway 1.00.03.AF1 BIOS, then you need to update your BIOS (see the README).
A fix is available from Gateway.
 
==941027 4030VL, Promise VLB Diskcaching Card IDE controller failed installing Warp.==
DESCRIPTION OF SYMPTOMS:
 
Even with cache disabled, the motherboard bios for disk I/O and all ide drives above 0 and 1 disconnected a complete failure with the repeated message that drive C is not available
and so forth all the way thru D and the logical drive partitions on both physical drives.
Note: the above is an example if the user has 2 physical drives connected to this Promise card.
   
   
==TITLE: 941028 Problem installing "Internet Connection for OS/2" portion of the Warp BonusPack from CDROM on Mitsumi CDROM drives.==
RESOLUTION:
 
Get a newer driver available from the Promise BBS.
The file is PTI1S506.ADD. When using this, the IBM1S506.ADD must be remmed out first. The older driver for DV4030VLIDE will not work.
 
==941028 Problem installing "Internet Connection for OS/2" portion of the Warp BonusPack from CDROM on Mitsumi CDROM drives==
;DESCRIPTION OF SYMPTOMS:
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:
   
   
DESCRIPTION OF SYMPTOMS:
The exit program for "IBM Internet Connection for OS/2" gave a bad return code of 65535. Continue with the
    User experiences XDFCOPY error message XDF3507 when trying
installation? If the user selects OK then the system will abort the install.
    to make the diskettes for the Internet portion of the Warp
 
    BonusPack. The error occurs ONLY on the INETCON1,2,3 &
;SUMMARY OF RESOLUTION:
    4.IMG files.  The rest of the BonusPack installs fine from
The user has the following options:
    the CDROM.
 
1.) 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.
 
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.) 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.
 
4.) If none of the above suggestions work, recommend that the user obtain a replacement BonusPack CDROM  
   
   
    If the user tries to install directly from the CDROM using
;DETAILS OF RESOLUTION:
    the BonusPack installation menu instead of making the
This problem has been observed to occur on Mitsumi CDROM drives (FX-001D and FX-100D). It may occur on others too.
    diskettes using XDFCOPY, he'll get UNZIP errors as shown
It appears to be a CDROM drive read problem. It is possible that the drive electronics and/or mechanics are not aligned
    below (in this example G:  is the CDROM drive letter):
(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
    g:\internet\iak1.zip" did not unzip correctly (rc=-51).
BonusPack components without error. The failure was only seen on the "Internet Connection for OS/2" component of the
    Do you wish to continue the installation?
Warp BonusPack CDROM.
 
    If the user chooses to continue installation he'll get the
==941103 INSTALLING S3964 DRIVERS ON WARP OS/2 VERSION 3.0 USING S3'S DRIVERS (THOSE WRITTEN BY S3 CORP.)==
    same error on iak2,3 & 4.zip files as well.  Finally the  
DESCRIPTION OF SYMPTOMS:
    BonusPack installation program will error out by reporting
 
    similar to the following:
Problems installing the S3 drivers for the S3 964 chip on system with OS/2 v3.0
# The install does not finish
    The exit program for "IBM Internet Connection for OS/2"
# The install hangs
    gave a bad return code of 65535. Continue with the
 
    installation?  If the user selects OK then the system will
SUMMARY OF RESOLUTION:
    abort the install.
# Edit the S3inst.cmd file
# Change all references to x:\os2 to x:\os2\boot.
SUMMARY OF RESOLUTION:
          (X: = drive where os2 resides)
    The user has the following options:
The drivers in original format will not install because the reference
the Os2 directory. Os2 v 3.0 installs the drivers into the Os2\Boot directory.
    1.) Try and run the XDFCOPY on another machine with a
 
        different CDROM drive.  The resulting diskettes can be
DETAILS OF RESOLUTION:
        used to install on the machine that is failing.
# Edit the S3INST.CMD file by:
#:a. Place the S3 driver diskette into the disk drive.
    2.) Have the customer attempt to copy the .IMG files from
#:b. Change to the disk drive
        the CDROM to a temporary subdirectory in his disk drive  
#:c. Pull S3INST.CMD into an editor
        and run XDFCOPY from the .IMG files on the disk drive.
# Change the reference from X:\OS2 TO X:\OS2\BOOT ('X' = drive where OS/2 resides)
 
    3.) Have the user check the BonusPack CDROM for any dirt or
Note: The drivers in the original format will not install since reference is to the \OS2 directory. OS/2 v3.0 installs drivers into the \OS2\BOOT directory
        scratches. CDROMs can suffer from the same read
 
        problems as audio CDs can. Also inspect the CD CADDY
==941114 Configuring the NEC 260 IDE cdrom under OS2 Warp==
        it is installed in or the CDROM drive drawer area for
;DESCRIPTION OF SYMPTOMS:
        any dust or dirt.
A NEC 260 IDE cdrom is not being recognized by OS2 Warp.
 
    4.) If none of the above suggestions work, recommend that
;SUMMARY OF RESOLUTION:
        the user obtain a replacement BonusPack CDROM
Make sure the proper drivers are loading in config.sys and that the necessary files are located in the proper directories.
 
;DETAILS OF RESOLUTION:
If you have already installed OS2 Warp, and are trying to get the cdrom recognized, follow these instructions:
   
   
DETAILS OF RESOLUTION:
# Go to the OS2 Selective Install utility. From the list of cdrom's, select the NEC 260. Click OK. At the System Configuration window, click OK again. At the Setup and Installation window, select the Install button.
    This problem has been observed to occur on Mitsumi CDROM
# Insert the OS2 diskette when prompted.
    drives (FX-001D and FX-100D).  It may occur on others too.
# Edit the OS2 config.sys in the root directory of the hard drive. Find the line:
    It appears to be a CDROM drive read problem.  It is possible
#:BASEDEV=IBM1S506.ADD
    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.
==TITLE: 941114 Configuring the NEC 260 IDE cdrom under OS2 Warp.==
DESCRIPTION OF SYMPTOMS:
    A NEC 260 IDE cdrom is not being recognized by OS2 Warp.
SUMMARY OF RESOLUTION:
    Make sure the proper drivers are loading in config.sys and
    that the necessary files are located in the proper directories.
DETAILS OF RESOLUTION:
    If you have already installed OS2 Warp, and are trying to get
                the cdrom recognized, follow these instructions:
      1. Go to the OS2 Selective Install utility. From the list of  
        cdrom's, select the NEC 260. Click OK. At the System  
        Configuration window, click OK again. At the Setup and  
        Installation window, select the Install button.
      2. Insert the OS2 diskette when prompted.
      3. Edit the OS2 config.sys in the root directory of the hard  
        drive. Find the line:
                          BASEDEV=IBM1S506.ADD
   
   
         Add switches to this line so that it reads:
         Add switches to this line so that it reads:
Line 126: Line 154:
   
   
           If you are trying to install Warp from the NEC 260 cdrom,
           If you are trying to install Warp from the NEC 260 cdrom,
           simply configure the BASEDEV=IBM1S506.ADD line per above.
           simply configure the BASEDEV=IBM1S506.ADD line per above.
           If you find that OS2 still does not recognize the cdrom,
           If you find that OS2 still does not recognize the cdrom,
           make sure that the /A and /U parameters are specified  
           make sure that the /A and /U parameters are specified
 
==941115 Warp TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT ==
DESCRIPTION OF SYMPTOMS:
 
When installing TCPIP Version 2.0 and The Internet Connection Kit
you will receive an error message that the products are not
supported when running TOGETHER. It will install, but there are
several problems and certain features will not work.
 
SUMMARY OF RESOLUTION:
 
Running TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT together under WARP is NOT supported.
   
   
==TITLE: 941027 4030VL, Promise VLB Diskcaching Card IDE controller failed installing Warp.==
DETAILS OF RESOLUTION:
 
Running TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT together under WARP is NOT supported.
 
==941115 RUNNING WEB EXPLORER UNDER WARP==
DESCRIPTION OF SYMPTOMS:
 
You can run Web Explorer under WARP version 3.0 as well as TCP-IP
version 2.0 with the base kit service pack for TCPIP 2.0.
 
SUMMARY OF RESOLUTION:
 
The customer will need obtain support from the Internet.
 
DETAILS OF RESOLUTION:
 
If the customer is running Web Explorer they must obtain support from the internet.
   
   
  DESCRIPTION OF SYMPTOMS:
The support news group on the internet newsgroup is:
    Even with cache disabled, the motherboard bios
  comp.os.os2.networking.tcp-ip
    for disk I/O and all ide drives above 0 and 1
 
    disconnected a complete failure with the
==941115 CHANGES MADE BY WARP TO WINDOWS FILES ==
    repeated message that drive C is not available
DESCRIPTION OF SYMPTOMS:
    and so forth all the way thru D and the logical
 
    drive partitions on both physical drives.
Changes to several Windows files occur during installation of OS/2 3.0 Warp
    Note: the above is an example if the user has 2 physical
 
    drives connected to this Promise card.
SUMMARY OF RESOLUTION:
 
The Following Windows files are Modified during WARP installation:
WIN.INI
SYSTEM.INI
WIN.COM
CONTROL.INI
PROGMAN.INI
SETUP.INF
CONTROL.INF
 
DETAILS OF RESOLUTION:
 
Changes to the following files are as follows:
 
WIN.INI
.Windows.
if no printer is defined in WINDOWS, Warp will
insert GENERIC / TEXT ONLY in the DEVICE= statement.
 
.Desktop.
Adds ICON SPACING=100
   
   
  RESOLUTION:
  note: this statement may or may not appear in this
    Get a newer driver available from the Promise BBS.
      section. If it does not, Warp will insert it
    The file is PTI1S506.ADD.  When using this, the
    IBM1S506.ADD must be remmed out first.  The older
    driver for DV4030VLIDE will not work.
   
   
==TITLE: 941026 THE SWAPPER FILE IN WARP.==
  .Ports.
   
DESCRIPTION OF SYMPTOMS:
    The swapper file is larger in WARP than in previous releases of
    OS2.
SUMMARY OF RESOLUTION:
    This is normal.
DETAILS OF RESOLUTION:
    This is normal.
    The most significant change that has been made is how system DLL's
    get loaded and what is now valid data for swapping.
    System DLL's include:
    DISPLAY          SOM          PMMERGE      PMWP
    DOSCALL1        PMATM        PMMLE
    IBMDEV32        PMCTLS      PMSPL
    IBMVGA32        PMGPI        PMVIOP
    In the previous versions of OS/2, dll code was never copied to the
    swapper file.  In WARP, code for system dll's can be written to
    the swapper file and, in adition, during boot, PMMERGE, DOSCALL1,
    PMGPI, PMWP and PMVIOP will be swapped out.  This means that there
    will be an overall increase in swapper size.  This was done
    to increase overall system perfomance.
==TITLE: 941115 Warp TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT ==
DESCRIPTION OF SYMPTOMS:
    When installing TCPIP Version 2.0 and The Internet Connection Kit
    you will receive an error message that the products are not
    supported when running TOGETHER.  It will install, but there are
    several problems and certain features will not work.
SUMMARY OF RESOLUTION:
    Running TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT together
    under WARP is NOT supported.
DETAILS OF RESOLUTION:
    Running TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT together
    under WARP is NOT supported.
== TITLE: 941121 TRAP0003 DISK #1 IBM1FLPY.ADD WARP OS/2. CS:EIP=0538:00001a21 CSLIM=000027d7.==
DESCRIPTION OF SYMPTOMS:
    Installing WARP disk #1 failed with TRAP0003 on the following
    values: CS:EIP=0538:00001a21 CSLIM=000027d7.
SUMMARY OF RESOLUTION:
    On the system setup bios, check the SETUP for the
    floppy drive setup.  Make sure that the floppy drive is setup
    correctly.  Example: If user has 1.44mb (3 1/2") drive, make
    sure the setup reflects 1.44mb setup instead of 1.2mb (5 1/4").
==TITLE: 941115 CHANGES MADE BY WARP TO WINDOWS FILES ==
DESCRIPTION OF SYMPTOMS:
    Changes to several Windows files occur during installation
    of OS/2 3.0 Warp
SUMMARY OF RESOLUTION:
    The Following Windows files are Modified during WARP installation:
    WIN.INI
    SYSTEM.INI
    WIN.COM
    CONTROL.INI
    PROGMAN.INI
    SETUP.INF
    CONTROL.INF
DETAILS OF RESOLUTION:
    Changes to the following files are as follows:
    WIN.INI
          .Windows.
          if no printer is defined in WINDOWS, Warp will
          insert GENERIC / TEXT ONLY in the DEVICE= statement.
          .Desktop.
          Adds ICON SPACING=100
          note:this statement may or may not appear in this
              section. If it does not, Warp will insert it
          .Ports.
           Adds .OS2 ports  
           Adds .OS2 ports  
   
   
          .Pscript.
.Pscript.
          This section is created and the following statements  
This section is created and the following statements  
          are added:
are added:
          EXTERNAL PRINTERS=6
EXTERNAL PRINTERS=6
          PRINTER1=40291760
PRINTER1=40291760
          PRINTER2=40291730
PRINTER2=40291730
          PRINTER3=40293930
PRINTER3=40293930
          PRINTER4=40293960
PRINTER4=40293960
          PRINTER5=IBM17521
PRINTER5=IBM17521
          PRINTER6=IBM39521
PRINTER6=IBM39521
   
   
          .Device.
.Device.
          This section is created and the following statement  
This section is created and the following statement  
          is inserted:
is inserted:
          GENERIC/TEXT ONLY TTY, LPT1:
GENERIC/TEXT ONLY TTY, LPT1:
   
   
          .Printer Ports.
.Printer Ports.
          This section is created and the following statement  
This section is created and the following statement  
          is inserted:
is inserted:
          GENERIC / TEXT ONLY=TTY,LPT1:,15,45
GENERIC / TEXT ONLY=TTY,LPT1:,15,45
   
   
    SYSTEM.INI
SYSTEM.INI
          .Boot.
.Boot.
          LANGUAGE.DLL= is modified to =LANGENG.DLL ( to ensure english)
LANGUAGE.DLL= is modified to =LANGENG.DLL (to ensure english)
        SYSTEM.DRV= is modified to =ATMSYS.DRV
SYSTEM.DRV= is modified to =ATMSYS.DRV
          MAVDMApps= is added  
MAVDMApps= is added  
          OS2MOUSE.DRV=MOUSE.DRV is added  
OS2MOUSE.DRV=MOUSE.DRV is added  
          ATM.SYSTEM.DRV=SYSTEM.DRV is added  
ATM.SYSTEM.DRV=SYSTEM.DRV is added  
          USEOS2SHIELD=1 is added  
USEOS2SHIELD=1 is added  
          OS2SHIELD=WINSHELD.EXE
OS2SHIELD=WINSHELD.EXE
   
   
          .Keyboard.
.Keyboard.
          KEYBOARD.DLL= is modofied to =KBDUS.DLL
KEYBOARD.DLL= is modofied to =KBDUS.DLL
   
   
          .386Enh.
.386Enh.
          MAY change the path in the PAGING FILE= statement  
MAY change the path in the PAGING FILE= statement  
          Changes the MAXPAGINGFILESIZE= statement  
Changes the MAXPAGINGFILESIZE= statement  
   
   
          .Timer.drv.
.Timer.drv.
          This section is created and the following statements are  
This section is created and the following statements are  
          inserted:
inserted:
          Max386Res=10
Max386Res=10
          Max286Res=10
Max286Res=10
   
   
    CONTROL.INI
CONTROL.INI
          .Installed.
.Installed.
          This section is created and the following statements  
This section is created and the following statements  
          are inserted:
are inserted:
          3.1=YES
3.1=YES
          HPPCL5A.DRV=yes
HPPCL5A.DRV=yes
          FINSTALL.DLL=YES
FINSTALL.DLL=YES
          FINSTALL.HLP=YES
FINSTALL.HLP=YES
          HPPCL5A.HLP=YES
HPPCL5A.HLP=YES
          HPPCL50P.HLP=YES
HPPCL50P.HLP=YES
          note: the reference to the HP universal print drivers are  
note: the reference to the HP universal print drivers are  
                due to an HP LaserJet being selected during install.
      due to an HP LaserJet being selected during install.
   
   
          .Function.
.Function.
          This section is created and the following statement is  
This section is created and the following statement is  
          inserted:
inserted:
          SETTINGS=COLORS, FONTS, PORTS, MOUSE, DESTOP, PRINTERS  
SETTINGS=COLORS, FONTS, PORTS, MOUSE, DESTOP, PRINTERS  
                  INTERNATIONAL, SOUND, NETWORK  
          INTERNATIONAL, SOUND, NETWORK  
   
   
    PROGMAN.INI
PROGMAN.INI
          .Settings.
.Settings.
          display.drv=<installed resolution> is inserted  
display.drv=<installed resolution> is inserted  
   
   
    SETUP.INF
SETUP.INF
          .oemdisks.
.oemdisks.
          A =. ,"IBM OS/2 Printer Driver Diskette 1","PMDD 1"
A =. ,"IBM OS/2 Printer Driver Diskette 1","PMDD 1"
          B =. ,"IBM OS/2 Printer Driver Diskette 2","PMDD 2"
B =. ,"IBM OS/2 Printer Driver Diskette 2","PMDD 2"
          C =. ,"IBM OS/2 Printer Driver Diskette 3","PMDD 3"
C =. ,"IBM OS/2 Printer Driver Diskette 3","PMDD 3"
 
==941121 TRAP0003 DISK #1 IBM1FLPY.ADD WARP OS/2. CS:EIP=0538:00001a21 CSLIM=000027d7.==
DESCRIPTION OF SYMPTOMS:
 
Installing WARP disk #1 failed with TRAP0003 on the following
values: CS:EIP=0538:00001a21 CSLIM=000027d7.
   
   
==TITLE: 941121 INSTALLING WARP, GETTING SYS0045 ON WINDOWS DISK #1==
SUMMARY OF RESOLUTION:
 
On the system setup bios, check the SETUP for the floppy drive setup. Make sure that the floppy drive is setup
correctly. Example: If user has 1.44mb (3 1/2") drive, make sure the setup reflects 1.44mb setup instead of 1.2mb (5 1/4").
 
==941121 INSTALLING WARP, GETTING SYS0045 ON WINDOWS DISK #1==
;DESCRIPTION OF SYMPTOMS:
 
Installing OS/ WARP passed the first phase and onto the second phase of the installation, when asks to insert the WINDOWS DISK #1, will received a " SYS0045 sector can't be found ... " If going into OS/2 and DIR on the WINDOWS DISKS, it is ok, but if trying to copy, xcopy any files from the WINDOWS DISKS to the hardfile, result the same error SYS0045 message.
 
;SUMMARY OF RESOLUTION:
 
User has changed the floppy drives around and did not update the CMOS to reflects the changes.
 
;DETAILS OF RESOLUTION:
 
User must go into the system CMOS and make sure the floppy drives are setup correctly.
 
Example: If changed the 1.44mb drive from B: to A:, and the 1.2mb drive from A: to B:, on the Setup on the CMOS should reflect that 1.44mb as an A: drive and 1.2mb as an B: drive.
 
==941121 WIN-OS2 SESSIONS FAIL TO LAUNCH. BOOTLOG.TXT HAS AS IT,S LAST STATEMENT, "LOADSTART=MOUSE.DRV"==
DESCRIPTION OF SYMPTOMS:
 
WIN-OS/2 fails to launch if there is no mouse type specified in MOUSE.INI
 
SUMMARY OF RESOLUTION:
 
Ensure the MOUSE.INI file has a type specified
 
DETAILS OF RESOLUTION:
 
When starting any WIN-OS/2 session (FS or Seamless), the session
will terminate before it starts. If initiated from an ICON, it
will hatch then unhatch. If initiated from a command line,
"Loading Please Wait..." will appear, then the session prompt
will re-display. If starting a WIN-OS/2 session from a command
line with a "/B" switch, the BOOTLOG.TXT file will show
LOADSTART=MOUSE.DRV as the last statement in the file. A look
at MOUSE.INI reveals "MOUSETYPE=". That statement MUST equal the
type of hardware installed on the system. When running in
DOS/WINDOWS, the system will query the hardware attached and
update MOUSE.INI accordingly. This is not occurring in OS/2.
APAR PJ16247 has been created to address this problem. Until
a resolution for the problem of why the MOUSE.INI file is not
being updated as it is in DOS/WINDOWS, ensure the MOUSETYPE=
statement in MOUSE.INI = <the mouse type described in the
boot.description section in system.
 
==941122 INSTALLING OS/2 WARP, INTERNAL CDROM DRIVE CONNECTED TO A SOUNDCARD DIRECTLY (NOT A SEPARATE CONTROLLER CARD).==
DESCRIPTION OF SYMPTOMS:
 
Not recognizing cdrom. OS2CDROM.DMD not found.
   
   
DESCRIPTION OF SYMPTOMS:
RESOLUTION:
    Installing OS/ WARP passed the first phase and onto the second
 
    phase of the installation, when asks to insert the WINDOWS
This is a hardware related problem. User needs to do the following:
    DISK #1, will received a " SYS0045 sector can't be found ... "
On the back of the cdrom drive is a jumper which controls the bus device number. OS/2 install requires it to be on 0 (zero).
    If going into OS/2 and DIR on the WINDOWS DISKS, it is ok, but if
Most sound board manufacturers leave it at the factory default of 1. If it is anything other than 0, the install disk #1 will  
    trying to copy, xcopy any files from the WINDOWS DISKS to the
not load the driver " OS2CDROM.DMD " and will stop installation with a red screen saying it can't find the cdrom.
    hardfile, result the same error SYS0045 message.
 
==941123 INSTALLING WARP ON A SYSTEM WITH FUTURE DOMAIN 1680, FIRST PHASE HANG WITH A BLINKING CURSOR. NO LOGO ON THE FIRST REBOOT.==
DESCRIPTION OF SYMPTOMS:
 
Installing WARP on a system with Future Domain 1680 SCSI controller and Toshiba 3401b CDROM, hang after the first reboot
with a blinking cursor on the top left hand corner. No logo, just a black screen with blinking cursor. This is on a 1.5gb
Maxtor hardfile.
 
SUMMARY OF RESOLUTION:
 
User has low-level formatted the hardfile under the Future Domain utilities, but did not partition the drive and high-level
format under this utilities. The Maxtor drive cylinders set is incorrect, showing 816 instead of actual 1014 cylinders. The
hardfile was NOT correctly defined previously therefore causing this problem.
 
DETAILS OF RESOLUTION:
 
Make sure the hardfile is correctly define and format under the Future Domain Utilities to avoid this problem.
 
==941123 INSTALLING WARP ON A SYSTEM WITH CDROM (TOSHIBA) CONNECTED TO AN ADAPTEC 1542C, GETTING A RED SCREEN NO CDROM DEVICE SUPPORT FOUND.==
DESCRIPTION OF SYMPTOMS:
 
Red screen on DISK #1, message no cdrom device support found.
   
   
SUMMARY OF RESOLUTION:
RESOLUTION:
    User has changed the floppy drives around and did not update
 
    the CMOS to reflects the changes.
Under the Adaptec setting option (Ctrl+A), disable the FAST
SCSI and Synchronize option.
This will enabled OS/2 WARP install DISK #1 to recognize the cdrom.
 
Note: The system has also a SoundBlaster card, but the cdrom (Toshiba) is connected to the Adaptec 1542C SCSI controller.
 
==941129 C0000005 ON DISK #1 INSTALLATION OF WARP CS:EIP = 013b : 00000ced CSLIM = 000025ab ==
DESCRIPTION OF SYMPTOMS:
   
   
DETAILS OF RESOLUTION:
Installation of WARP, on Disk 1 received the following error:
    User must go into the system CMOS and make sure the floppy
A program in this session encountered a problem and  
    drives are setup correctly.
cannot continue.
    Example: If changed the 1.44mb drive from B: to A:, and the 1.2mb
c0000005
              drive from A: to B:, on the Setup on the CMOS should
P1 =00000000 P2 =ffffffff P3 =xxxxxxxx P4 =xxxxxxxx
              reflect that 1.44mb as an A: drive and 1.2mb as an B:
EAX=00000002 EBX=ffe4a814 ECX=00000041 EDX=ffe28c44
              drive.
ESI=ffe4000a EDI=ff3f0008
DS=03cb  DSACC=00f3  DSLIM=000007ff
ES=0130  ESACC=00f3  ESLIM=00005133
FS=0000  FSACC=****  FSLIM=********
GS=0000  GSACC=****  GSLIM=********
CS:EIP=013b:00000ced CSACC=00fb  CSLIM=000025ab
SS:EIP=0017:00000fc6 SSACC=00f3  SSLIM=00000fff
EBP=00000433 FLG=00013202
 
SUMMARY OF RESOLUTION:
   
   
==TITLE: 941121 WIN-OS2 SESSIONS FAIL TO LAUNCH. BOOTLOG.TXT HAS AS IT,S LAST STATEMENT, "LOADSTART=MOUSE.DRV"==
Check the CONFIG.SYS, user has edited this file and instead of putting " REM " for remarks out the statement, user put a non-
alphabet characters. For example, instead of the following:
REM basedev=ibm1s506.add
user has put
;basedev=ibm1s506.add  (a semi-colon " ; ")
This above will result the c0000005 error on disk #1.
   
   
DESCRIPTION OF SYMPTOMS:
DETAILS OF RESOLUTION:
    WIN-OS/2 fails to launch if there is no mouse type specified
    in MOUSE.INI
   
   
SUMMARY OF RESOLUTION:
Make sure the user does not use any non alphabet characters for any statements on the config.sys.
    Ensure the MOUSE.INI file has a type specified
Under OS/2, everytime a statement needs to be REMarks out, user REM instead of ";" or non alphabet characters.
 
DETAILS OF RESOLUTION:
==941129 WARP PACKAGE UPDATE - HOW TO FIND OUT WHICH WARP PACKAGE THE CUSTOMER RECEIVED==
    When starting any WIN-OS/2 session (FS or Seamless), the session
;DESCRIPTION OF SYMPTOMS:
    will terminate before it starts. If initiated from an ICON, it
 
    will hatch then unhatch. If initiated from a command line,
How to tell which WARP Package the customer is running.
    "Loading Please Wait..." will appear, then the session prompt
 
    will re-display. If starting a WIN-OS/2 session from a command
;SUMMARY OF RESOLUTION:
    line with a "/B" switch, the BOOTLOG.TXT file will show
 
    LOADSTART=MOUSE.DRV as the last statement in the file. A look
Check the manufactured packages.
    at MOUSE.INI reveals "MOUSETYPE=". That statement MUST equal the
The SYSINST1.EXE file has been updated.
    type of hardware installed on the system. When running in
 
    DOS/WINDOWS, the system will query the hardware attached and
;DETAILS OF RESOLUTION:
    update MOUSE.INI accordingly. This is not occurring in OS/2.
 
    APAR PJ16247 has been created to address this problem. Until
The only file that was changed in the updated WARP Package is SYSINST1.EXE. This file is located on Disk 1 or CD Rom 1 and is installed to:
    a resolution for the problem of why the MOUSE.INI file is not
X:\OS2\INSTALL\BOOTDISK\SYSINST1.EXE
    being updated as it is in DOS/WINDOWS, ensure the MOUSETYPE=
The old file size for SYSINST1.EXE is 4992 bytes, dated 10-08-94.
    statement in MOUSE.INI = <the mouse type described in the
The new file size for SYSINST1.EXE is 4960 bytes, dated 10-25-94.
    boot.description section in syste
 
----
==TITLE: 941115 RUNNING WEB EXPLORER UNDER WARP==
The following should be used to distinguish the original GA version of WARP from the updated packages, or from newly manufactured packages.
 
DESCRIPTION OF SYMPTOMS:
# 16-Digit Code on Bottom of WARP Box (1st 6 Digits are Date of Mfg)
    You can run Web Explorer under WARP version 3.0 as well as TCP-IP
#* If Down-Level (not reworked) will have date prior to 10/29/94
    version 2.0 with the base kit service pack for TCPIP 2.0.
#* If Reworked, will have Original Code w/date prior to 10/29/94 PLUS Additional 16-Digit Code that will reflect date of rework
#* Single 16-Digit Code w/date After 10/29, reflects newly Manufactured Product, w/revised code.
SUMMARY OF RESOLUTION:
# Shipping Carton of any "REWORKED" Product will have a single WHITE STICKER (no text) on outside of Box. White sticker will be visible thru pallet.
    The customer will need obtain support from the Internet.
# Diskette Label of Diskette 1 has revised Part Number (P/N):
#: 83G8658 (for Diskette Version)
DETAILS OF RESOLUTION:
#: 83G8661 (for CD-ROM Version)
    If the customer is running Web Explorer they must obtain support
 
    from the internet.
==941130 TRAP000E WITH CS:EIP 0160:FFF6EFBE==
DESCRIPTION OF SYMPTOMS:
    The support news group on the internet newsgroup is:
 
        comp.os.os2.networking.tcp-ip
Customer receives a Trap000e with cs:eip 0160:FFF6EFBE when running laps WR06000 and/or lan server IP07000. The function name which is failing is _VMGetSem.
 
==TITLE: 941122 INSTALLING OS/2 WARP, INTERNAL CDROM DRIVE CONNECTED TO A SOUNDCARD DIRECTLY (NOT A SEPARATE CONTROLLER CARD).==
SUMMARY OF RESOLUTION:
 
DESCRIPTION OF SYMPTOMS:
Customer must upgrade to the latest csd's for Laps and Lan server. (WR07045 and IP07045)
    Not recognizing cdrom.  OS2CDROM.DMD not found.
 
DETAILS OF RESOLUTION:
RESOLUTION:
 
    This is a hardware related problem.  User needs to do the
If a customer receives a Trap000E with CS:EIP 0160:FFF6EFBE they must upgrade their Laps to WR07045 and Lan Server to IP07045.
    following:
 
    On the back of the cdrom drive is a jumper which controls the bus
NOTE: This may not necessarily pertain to Laps and Lan Server. If the customer is running any other Product such as Novell, other Lan software, or specific drivers make sure they are updated to the latest version.
    device number.  OS/2 install requires it to be on 0 (zero).
 
    Most sound board manufacturers leave it at the factory default
==941201 Philips cdrom causes boot problem if /m parameter used ==
    of 1. If it is anything other than 0, the install disk #1 will
DESCRIPTION OF SYMPTOMS:
    not load the driver " OS2CDROM.DMD " and will stop installation
 
    with a red screen saying it can't find the cdrom.
After setting the number of 2500 byte CD frame buffers to a value greater than the default value, OS2 will not boot. The default value is 16, the maximum 26, and the minimum 8. If customer is loading the LMS205.ADD driver, the line in config.sys would read
  BASEDEV=LMS205.ADD /m:26
==TITLE: 941123 INSTALLING WARP ON A SYSTEM WITH FUTURE DOMAIN 1680, FIRST PHASE HANG WITH A BLINKING CURSOR.  NO LOGO ON THE FIRST REBOOT.==
to specify 26 2500 byte CD frame buffers.
 
DESCRIPTION OF SYMPTOMS:
With the Philips 206 cdrom, the line would read
    Installing WARP on a system with Future Domain 1680 SCSI
BASEDEV=LMS206.ADD /m:
    controller and Toshiba 3401b CDROM, hang after the first reboot
 
    with a blinking cursor on the top left hand corner. No logo,
SUMMARY OF RESOLUTION:
    just a black screen with blinking cursor. This is on a 1.5gb
 
    Maxtor hardfile.
Change the number of CD frame buffers back to the default value.
   
 
SUMMARY OF RESOLUTION:
DETAILS OF RESOLUTION:
    User has low-level formatted the hardfile under the Future Domain
 
    utilities, but did not partition the drive and high-level
Please follow these instructions:
    format under this utilities. The Maxtor drive cylinders set is
# Bring up the OS2 config.sys in an editor.
    incorrect, showing 816 instead of actual 1014 cylinders.  The
# Check the config.sys for the statements<br/>BASEDEV=LMS205.ADD /m:26
    hardfile was NOT correctly defined previously therefore causing
# Remove the /m:26 so the line reads<br/>BASEDEV=LMS205.ADD
    this problem.
# Save the file, shutdown and reboot for the changes to take effect.
 
DETAILS OF RESOLUTION:
== 941205 GENERAL PROBLEMS ON INSTALLATION OF WARP, MAINTENANCE DESKTOP OR BEFORE THE FINAL REBOOT==  
    Make sure the hardfile is correctly define and format under the  
DESCRIPTION OF SYMPTOMS:
    Future Domain Utilities to avoid this problem.
 
# Customer receives sys3175 in os2mm.dll (PJ16290) on first reboot or Maintenance Desktop.
==TITLE: 941123 INSTALLING WARP ON A SYSTEM WITH CDROM (TOSHIBA) CONNECTED TO AN ADAPTEC 1542C, GETTING A RED SCREEN NO CDROM DEVICE SUPPORT FOUND.==
# Customer receives sys3175 in unpack2.exe, when continuing installation through the maintenance desktop on any diskette.
# OS2 is unable to operate your hard disk or your diskette drive.
DESCRIPTION OF SYMPTOMS:
# System hangs on maintenance desktop.
    Red screen on DISK #1, message no cdrom device support found.
# System beeps on diskette #7 when asking for the diskette.
 
RESOLUTION:
RESOLUTION:
    Under the Adaptec setting option (Ctrl+A), disable the FAST
 
    SCSI and Synchronize option.
Remark out the basedev=xxxxxxx.add from config.sys on the harddrive except ibmint13.i13 and ibm%flpy.add and the cdrom
    This will enabled OS/2 WARP install DISK #1 to recognize the
controller device driver (Where xxxxxx can be any character and % is replaced by 2 for microchannel system and a 1 if any other system).
    cdrom.
Also refer customer for possible 174 in Users Guide to OS/2 book additional explanation and actions.
    Note: The system has also a SoundBlaster card, but the
If customer has Ethernet Card (NE2000 Compatible), ask to customer to remove it (PJ15955).
    cdrom (Toshiba) is connected to the Adaptec 1542C SCSI
 
    controller.
==941207 WARP ERROR MESSAGE "DRIVE X NOT READY PRESS ANY KEY"==
DESCRIPTION OF SYMPTOMS:
==TITLE: 941129 C0000005 ON DISK #1 INSTALLATION OF WARP CS:EIP = 013b : 00000ced CSLIM = 000025ab ==
 
CUSTOMERS USING THE BOOT MANAGER FEATURE UNDER OS/2 WARP MAY GET THE ERROR MESSAGE "DRIVE 1 NOT READY PRESS ANY KEY" AND THE SYSTEM BOOTS NORMALLY. OTHER DRIVES NUMBERS MAY ALSO BE REPORTED AS NOT READY. THIS IS MOST PREVALENT ON COMPUTERS THAT UTILIZE A SCSI HOST ADAPTER.
DESCRIPTION OF SYMPTOMS:
 
SUMMARY OF RESOLUTION:
    Installation of WARP, on Disk 1 received the following error:
 
    "A program in this session encountered a problem and
THE CUSTOMER SHOULD CHECK THE HARDWARE SETTINGS OF ALL THE DRIVES IN HIS SYSTEM. ON SYSTEMS WITH SCSI HOST ADAPTERS, BE CERTAIN THAT ONLY BOOTABLE DRIVES HAVE A SCSI ID OF 0 OR 1. USING FDISK FROM A PREVIOUS VERSION OF OS/2 TO INSTALL THE BOOTMANAGER WILL CIRCUMVENT THE MESSAGE.
      cannot continue.
 
      c0000005
DETAILS OF RESOLUTION:
      P1 =00000000 P2 =ffffffff P3 =xxxxxxxx P4 =xxxxxxxx
 
      EAX=00000002 EBX=ffe4a814 ECX=00000041 EDX=ffe28c44
THE ERROR MESSAGE APPEARING IS THE RESULT OF ADDITIONAL MESSAGEING THAT WAS ADDED TO ALERT A USER THAT AN EXTERNAL DRIVE MAY NOT BE POWERED ON. ONE OF THE REASONS THAT IT APPEARS FOR WARP USERS WITHOUT EXTERNAL DRIVES MAY BE A NON STANDARD IMPLENTATION OF THE BIOS IN THE USERS SCSI CARD. USING THE FDISK PROGRAM FROM A PREVIOUS VERSION OF OS/2 WILL STOP THE ERROR MESSAGE FROM APPEARING. FDISK.COM IS LOCATED ON DISK 1 OF MOST VERSIONS OF OS/2 INSTALLATION DISKETTES, IT IS ALSO IN THE \OS2SE21\DISK_2 DIRECTORY OF MOST OS/2 CDROMS.
      ESI=ffe4000a EDI=ff3f0008
 
      DS=03cb  DSACC=00f3  DSLIM=000007ff
==941207 IPE 0160:FFFBA0FC - 000D:000680FC, 1163, 7019 ON DISK 1 INTERNAL REVISION 8.162 94/09/19==
      ES=0130  ESACC=00f3  ESLIM=00005133
DESCRIPTION OF SYMPTOMS:
      FS=0000  FSACC=****  FSLIM=********
 
      GS=0000  GSACC=****  GSLIM=********
Installing WARP on Disk #1 when the user replaced the IBMKBD.SYS with the size of 29,525, will get the following IPE.
      CS:EIP=013b:00000ced CSACC=00fb  CSLIM=000025ab
  *************** IPE 16/32-bit *************************
      SS:EIP=0017:00000fc6 SSACC=00f3  SSLIM=00000fff
  THE SYSTEM DETECTED AN INTERNAL PROCESSING
      EBP=00000433 FLG=00013202
    ERROR AT LOCATION # 0160:fffba0fc - 000d:000680fc
    1163, 7019
SUMMARY OF RESOLUTION:
  048600b4
  INTERNAL REVISION  8.162     94/09/19
    Check the CONFIG.SYS, user has edited this file and instead of
  *********** end IPE 16/32-bit ************************
    putting " REM " for remarks out the statement, user put a non-
 
    alphabet characters. For example, instead of the following:
RESOLUTION:
    REM basedev=ibm1s506.add
 
    user has put
User has downloaded the wrong IBMKBD.SYS file.
    ;basedev=ibm1s506.add  (a semi-colon " ; ")
The file size should be 4,677 and dated 7/30/94.
    This above will result the c0000005 error on disk #1.
Note: this file is the temporarily fix for PJ16077
DETAILS OF RESOLUTION:
    Make sure the user does not use any non alphabet characters for
    any statements on the config.sys.
    Under OS/2, everytime a statement needs to be REMarks out,
    user REM instead of ";" or non alphabet characters.
== TITLE: 941205 GENERAL PROBLEMS ON INSTALLATION OF WARP, MAINTENANCE DESKTOP OR BEFORE THE FINAL REBOOT==
DESCRIPTION OF SYMPTOMS:
    1. Customer receives sys3175 in os2mm.dll (PJ16290) on first
        reboot or Maintenance Desktop.
    2. Customer receives sys3175 in unpack2.exe, when continuing
        installation through the maintenance desktop on any diskette.
    3. OS2 is unable to operate your hard disk or your diskette drive.
    4. System hangs on maintenance desktop.
    5. System beeps on diskette #7 when asking for the diskette.
   
RESOLUTION:
    Remark out the basedev=xxxxxxx.add from config.sys on the harddrive
    except ibmint13.i13 and ibm%flpy.add and the cdrom
    controller device driver (Where xxxxxx can be any character and % is
    replaced by 2 for microchannel system and a 1 if any other system).
     Also refer customer for possible 174 in Users Guide to OS/2 book
    additional explanation and actions.
    If customer has Ethernet Card (NE2000 Compatible), ask to
    customer to remove it (PJ15955).
   
==TITLE: 941103 INSTALLING S3964 DRIVERS ON WARP OS/2 VERSION 3.0 USING S3'S DRIVERS (THOSE WRITTEN BY S3 CORP.)==
DESCRIPTION OF SYMPTOMS:
    Problems installing the S3 drivers for the S3 964 chip on system with
    OS/2 v3.0
        1.  The install does not finish
        2.  The install hangs
SUMMARY OF RESOLUTION:
    1.  Edit the S3inst.cmd file
    2.  Change all references to x:\os2 to x:\os2\boot.
          (X: = drive where os2 resides)
    The drivers in original format will not install because the reference
    the Os2 directory.  Os2 v 3.0 installs the drivers into the Os2\Boot
    directory.
DETAILS OF RESOLUTION:
    1.  Edit the S3INST.CMD file by:
          a.  Place the S3 driver diskette into the disk drive.
          b.  Change to the disk drive
          c.  Pull S3INST.CMD into an editor
    2.  Change the reference from X:\OS2 TO X:\OS2\BOOT
          ('X' = drive where OS/2 resides)
          Note: The drivers in the original format will not install since
                  reference is to the \OS2 directory.  OS/2 v3.0 installs
                  drivers into the \OS2\BOOT directory
==TITLE: 941129 WARP PACKAGE UPDATE - HOW TO FIND OUT WHICH WARP PACKAGE THE CUSTOMER RECEIVED==
DESCRIPTION OF SYMPTOMS:
    How to tell which WARP Package the customer is running.
SUMMARY OF RESOLUTION:
    Check the manufactured packages.
    The SYSINST1.EXE file has been updated.
DETAILS OF RESOLUTION:
    The only file that was changed in the updated WARP Package is
    SYSINST1.EXE.  This file is located on Disk 1 or CD Rom 1 and
    is installed to:
          X:\OS2\INSTALL\BOOTDISK\SYSINST1.EXE
    The old file size for SYSINST1.EXE is 4992 bytes, dated 10-08-94.
    The new file size for SYSINST1.EXE is 4960 bytes, dated 10-25-94.
                        ************************
  The following should be used to distinguish the original GA
  version of WARP from the updated packages, or from newly
  manufactured packages.
  1. 16-Digit Code on Bottom of WARP Box (1st 6 Digits are Date of Mfg)
    - If Down-Level (not reworked) will have date prior to 10/29/94
    - If Reworked, will have Original Code w/date prior to 10/29/94
      PLUS Additional 16-Digit Code that will reflect date of rework
    - Single 16-Digit Code w/date After 10/29, reflects newly
      Manufactured Product, w/revised code.
  2. Shipping Carton of any "REWORKED" Product will have a single
    WHITE STICKER (no text) on outside of Box.  White sticker will
    be visible thru pallet.
  3. Diskette Label of Diskette 1 has revised Part Number (P/N):
    83G8658 (for Diskette Version)
    83G8661 (for CD-ROM Version)
==TITLE: 941130 TRAP000E WITH CS:EIP 0160:FFF6EFBE==
DESCRIPTION OF SYMPTOMS:
    Customer receives a Trap000e with cs:eip 0160:FFF6EFBE when
    running laps WR06000 and/or lan server IP07000.  The function
    name which is failing is _VMGetSem.
SUMMARY OF RESOLUTION:
    Customer must upgrade to the latest csd's for Laps and Lan
    server.  (WR07045 and IP07045)
DETAILS OF RESOLUTION:
    If a customer receives a Trap000E with CS:EIP 0160:FFF6EFBE they
    must upgrade their Laps to WR07045 and Lan Server to IP07045.
    NOTE:  This may not necessarily pertain to Laps and Lan Server.  If
    the customer is running any other Product such as Novell, other
    Lan software, or specific drivers make sure they are updated to
    the latest version.
==TITLE: 941209 System hangs with Adaptec 2740/2742 controller with cdrom attached.==
DESCRIPTION OF SYMPTOMS:
    Attempting to access a CDROM attached to an Adaptec 2740/2742
    scsi controller causes trap or system hang.
SUMMARY OF RESOLUTION:
    Disable tagged queing for the AIC7770.ADD driver.
DETAILS OF RESOLUTION:
    1. Edit the OS2 config.sys file.
    2. Change the line
        BASEDEV=AIC7770.ADD
                  to
        BASEDEV=AIC7770.ADD /A:0 /TAG:1
    3. Shut down system and then reboot for change to take effect.
==TITLE: 941208 SHUTDOWN FAILS UNDER OS/2 2.11 OR WARP DUE TO LOTUS CC:MAIL BEING ON THE SYSTEM ==
DESCRIPTION OF SYMPTOMS:
    In some cases, after installing CCMail Client on a system running
    WARP 3.0, the user will be unable to successfully shutdown.
SUMMARY OF RESOLUTION:
    CCmail is aware of this and the 1.04 build will address this
    issue.
DETAILS OF RESOLUTION:
    To work around this problem:
        Make sure the user either has their CCMail folder open, or
        places a shadow of any object within the CCMail folder on the
        OS/2 desktop, prior to shutdown.
    ALSO, word from a Lotus support tech is that if the IN BOX has a
    shadow on the Desktop, then the problem will not occur.
    This problem will be addressed in the version 1.04 of CCmail.
    The most current version of CCMail Client is 1.03 and 1.04 is
    scheduled to be available early 1995.
==TITLE: 941207 WARP ERROR MESSAGE "DRIVE X NOT READY PRESS ANY KEY"==
DESCRIPTION OF SYMPTOMS:
    CUSTOMERS USING THE BOOT MANAGER FEATURE UNDER OS/2 WARP MAY GET
    THE ERROR MESSAGE "DRIVE 1 NOT READY PRESS ANY KEY" AND THE SYSTEM
    BOOTS NORMALLY. OTHER DRIVES NUMBERS MAY ALSO BE REPORTED AS NOT
    READY. THIS IS MOST PREVALENT ON COMPUTERS THAT UTILIZE A SCSI
    HOST ADAPTER.
SUMMARY OF RESOLUTION:
    THE CUSTOMER SHOULD CHECK THE HARDWARE SETTINGS OF ALL THE
    DRIVES IN HIS SYSTEM. ON SYSTEMS WITH SCSI HOST ADAPTERS, BE
    CERTAIN THAT ONLY BOOTABLE DRIVES HAVE A SCSI ID OF 0 OR 1.
    USING FDISK FROM A PREVIOUS VERSION OF OS/2 TO INSTALL THE
    BOOTMANAGER WILL CIRCUMVENT THE MESSAGE.
DETAILS OF RESOLUTION:
    THE ERROR MESSAGE APPEARING IS THE RESULT OF ADDITIONAL
    MESSAGEING THAT WAS ADDED TO ALERT A USER THAT AN EXTERNAL
    DRIVE MAY NOT BE POWERED ON. ONE OF THE REASONS THAT IT APPEARS
    FOR WARP USERS WITHOUT EXTERNAL DRIVES MAY BE A NON STANDARD
    IMPLENTATION OF THE BIOS IN THE USERS SCSI CARD. USING
    THE FDISK PROGRAM FROM A PREVIOUS VERSION OF OS/2 WILL STOP
    THE ERROR MESSAGE FROM APPEARING. FDISK.COM IS LOCATED ON DISK 1
    OF MOST VERSIONS OF OS/2 INSTALLATION DISKETTES, IT IS ALSO IN THE
    \OS2SE21\DISK_2 DIRECTORY OF MOST OS/2 CDROMS.
==TITLE: 941207 IPE 0160:FFFBA0FC - 000D:000680FC, 1163, 7019 ON DISK 1 INTERNAL REVISION 8.162 94/09/19==
DESCRIPTION OF SYMPTOMS:
    Installing WARP on Disk #1 when the user replaced the IBMKBD.SYS
    with the size of 29,525, will get the following IPE.
    *************** IPE 16/32-bit *************************
      THE SYSTEM DETECTED AN INTERNAL PROCESSING
      ERROR AT LOCATION # 0160:fffba0fc - 000d:000680fc
        1163, 7019
      048600b4
      INTERNAL REVISION  8.162      94/09/19
    *********** end IPE 16/32-bit ************************
RESOLUTION:
    User has downloaded the wrong IBMKBD.SYS file.
    The file size should be 4,677 and dated 7/30/94.
    Note: this file is the temporarily fix for PJ16077
==TITLE: 941209 WHAT IDE CD-ROMS ARE COMPATIBLE WITH OS2 Warp? AND HOW DO I MAKE THEM WORK?==
DESCRIPTION OF SYMPTOMS:
    CDROM NOT WORKING UNDER WARP
SUMMARY OF RESOLUTION:
    What Follows is a list of CD-ROMs that are known to be compatible
    with Warp and how to make them work.
DETAILS OF RESOLUTION:
    The IDE hard disk driver, IBM1S506.ADD, was made aware of ATAPI.
    This driver will claim all ATAPI devices and mark them as generic
    devices. The IBMIDECD.FLT filter loads afterwards and scans all
    drivers for generic ATAPI devices. If it locates one, it will decide
    if that device is a CDROM.
    Note:  In addition to IBM1S506.ADD and IBMIDECD.FLT, all CD-ROM
    in the table below require the OS2CDROM.DMD and CDFS.IFS device
    These are added automatically when the selective install is done.
    CDROM.
    An IDE CDROM cannot be a master while a hard drive is being a slave.
    You cannot use the IBMINT13.I13 for an IDE CDROM.
          -------------------------------------
          Manufacturer  |Model      |  Notes  |
          --------------|-----------|---------|
          Mitsumi      |FX001DE    |    1    |
          ------------------------------------|
          NEC          |CDR-250    |        |
                        |CDR-260    |    2    |
                        |NEC 2vi    |        |
          ------------------------------------|
          Sony          |55E        |    1    |
                        |55D        |    1    |
          ------------------------------------|
          Panasonic    |571        |        |
          ------------------------------------|
          Wearnes      |CDD-120    |        |
          -------------------------------------
    Notes:
    1. The Mitsumi and Sony cdroms may have problems because they are not
        ATAPI 1.2 compliant. This should be fixed with updated drivers.
    2. NEC 260 cdroms that ship with some Gateway systems adhere to the
        1.7 spec instead of 1.2. For these cdroms, the BASEDEV=IBM1S506. A
        line in the OS2 config.sys file has to be edited as follows:
                BASEDEV=IBM1S506.ADD /A:x /U:y /ATAPI
        The /A switch refers to the adapter number that the cdrom
        is attached to. The /U option references the unit or device
        number on a particular adapter. The /ATAPI parameter
        enables ATA Packet Interface protocol for the NEC 260. If the
        cdrom is attached to the second IDE port or adapter in a
        system and is the only device on the adapter you would
        enter:
                BASEDEV=IBM1S506.ADD /A:1 /U:0 /ATAPI
==TITLE: 941201 Philips cdrom causes boot problem if /m parameter used ==
DESCRIPTION OF SYMPTOMS:
    After setting the number of 2500 byte CD frame buffers to a value
    greater than the default value, OS2 will not boot. The default value
    is 16, the maximum 26, and the minimum 8. If customer is loading
    the LMS205.ADD driver, the line in config.sys would read
              BASEDEV=LMS205.ADD /m:26
    to specify 26 2500 byte CD frame buffers.
    With the Philips 206 cdrom, the line would read
              BASEDEV=LMS206.ADD /m:
SUMMARY OF RESOLUTION:
    Change the number of CD frame buffers back to the default value.
DETAILS OF RESOLUTION:
    Please follow these instructions:
    1. Bring up the OS2 config.sys in an editor.
    2. Check the config.sys for the statements
        BASEDEV=LMS205.ADD /m:26
    3. Remove the /m:26 so the line reads
        BASEDEV=LMS205.ADD
    4. Save the file, shutdown and reboot for the changes to take
        effect.
October 25, 1995
                    Personal Systems Support Family
                        Platform Offering Options
  ----------------------------------------------------------------------
  +--------------------------------------------------------------------+
  | Figure 1 (Page 1 of 2). Platform Offering Options                  |
  +--------------+-----------------+-----------------+-----------------+
  |              | SUPPORT LINE    | SUPPORT LINE    | SUPPORT LINE    |
  |              | PER INCIDENT    | STANDARD        | PREMIUM        |
  +--------------+-----------------+-----------------+-----------------+
  | Fees        | $190 Per        | $4,495 for      | $29,995 for    |
  |              | Incident        | Unlimited      | Unlimited      |
  |              |                | Incidents      | Incidents      |
  |              |                | ($4,050 with    | ($28,645 with  |
  |              |                | certification)  | certification)  |
  +--------------+-----------------+-----------------+-----------------+
  | Support for  | Not Applicable  | Priced Per      | All products    |
  | Additional  |                | Product Added  | are included    |
  | Products    |                |                |                |
  +--------------+-----------------+-----------------+-----------------+
  | Support      | 8 AM to 5 PM    | 8 AM to 5 PM    | 24 X 7          |
  | Hours        | Customer Time  | Customer Time  | (excluding      |
  |              | Zone - Monday  | Zone - Monday  | Christmas Day)  |
  |              | through Friday  | through Friday  |                |
  |              | (excluding U.S. | (excluding U.S. |                |
  |              | national        | national        |                |
  |              | holidays)      | holidays)      |                |
  +--------------+-----------------+-----------------+-----------------+
  | 24 X 7      | $260 Per        | $1,575          | Included        |
  | Coverage    | Incident        | additional      |                |
  |              |                | ($6,070 total  |                |
  |              |                | includes the    |                |
  |              |                | base operating  |                |
  |              |                | system)*        |                |
  +--------------+-----------------+-----------------+-----------------+
  | Priority    | Not Applicable  | $4,995          | Included        |
  | Handling    |                | additional      |                |
  +--------------+-----------------+-----------------+-----------------+
  | Customer    | Not Applicable  | 2 primary / 2  | 6 primary / 6  |
  | Contacts    |                | alternates      | alternates      |
  | Included    |                |                | (includes 2    |
  |              |                |                | primary and 2  |
  |              |                |                | alternates for  |
  |              |                |                | extended hours  |
  |              |                |                | coverage)      |
  +--------------+-----------------+-----------------+-----------------+
  | Additional  | Not Applicable  | $2,995 each    | $2,995 each    |
  | Customer    |                |                |                |
  | Contacts    |                |                |                |
  +--------------+-----------------+-----------------+-----------------+
  | Multivendor  | Not Applicable  | $1,995          | Included        |
  | Coordination |                | additional      |                |
  +--------------+-----------------+-----------------+-----------------+
  |              | SUPPORT LINE    | SUPPORT LINE    | SUPPORT LINE    |
  |              | PER INCIDENT    | STANDARD        | PREMIUM        |
  +--------------+-----------------+-----------------+-----------------+
  | Monthly      | Not Applicable  | Included        | Included        |
  | Activity    |                |                |                |
  | Reports      |                |                |                |
  +--------------+-----------------+-----------------+-----------------+
  | NOTE:  * The charge for Extended Hours Coverage includes the      |
  | OPERATING SYSTEM ONLY.  24 X 7 coverage for each additional        |
  | product is subject to a 35% premium of the cost of support for    |
  | that product, on a product-by-product basis, and must be added to  |
  | the base charge.                                                  |
  |                                                                    |
  | A 10% discount will apply for multiple purchases of either Support |
  | Line Standard or Support Line Premium.  Discounts do not apply to  |
  | optional charges.                                                  |
  +--------------------------------------------------------------------+
************************************************************************                   
Personal Systems Support Family                                   
Fees 
---------------------------------------------------------------------- 
PERSONAL SYSTEMS FORUM  o  Forum - No charge  o 
IBM  TalkLink  Fee  -  $18  per  month (plus one-time
registration      charge of $15)    PERSONAL SYSTEMS
TECHNICAL CONNECTION PERSONAL SOFTWARE CD-ROM  o 
Single copy - $59  o  Annual Subscription - Quarterly
updates $119  o  Annual Subscription - Monthly updates
$299  PERSONAL SYSTEMS CONSULT LINE, PER HOUR
(MINIMUM OF 1 HOUR)  $240  IBM HOUSE CALL, PER HOUR
(MINIMUM OF 2 HOURS)  o  Hourly - $170  o  2 - 19
Hours - $170 per hour  o  20 -99 Hours - $155 per hour  o 
100+ Hours - $140 per hour    CUSTOMER APPLICATION
ASSISTANCE, PER HOUR  $240  DESKTOP APPLICATION
SUPPORT  o  $64 per Incident  o  $600 for 10 Incidents 
TECHNICAL SOLUTIONS  Annual Subscription - $50 
***********************************************************************                   
Personal Systems Support Family                        Single
User Services Options 
----------------------------------------------------------------------


  +--------------------------------------------------------------------+
==941207 USER MAY GET SYS3175 IN INSTALL.EXE WHILE INSTALLING WARP ON ZEOS PANTERA SYSTEM.==
  | Figure 2. Single User Services Options                            |
  +--------------+-----------------+-----------------+-----------------+
  |              | SINGLE INCIDENT | SINGLE INCIDENT | UNLIMITED      |
  |              | - 800 #        | - 900 #        | INCIDENTS      |
  +--------------+-----------------+-----------------+-----------------+
  | Contract    | Single Incident | Single Incident | Annual          |
  | Period      |                |                |                |
  +--------------+-----------------+-----------------+-----------------+
  | Fees        | $45.00 Per      | $2.00 Per      | $179.00 Per    |
  |              | Incident        | Minute, $50    | Year            |
  |              |                | Maximum Per    |                |
  |              |                | Incident        |                |
  +--------------+-----------------+-----------------+-----------------+
  | Standard    | OS/2 & DOS      | OS/2 & DOS      | OS/2 & DOS      |
  | Products    |                |                | (limited        |
  |              |                |                | product set)    |
  +--------------+-----------------+-----------------+-----------------+
  | Extended    | N/A            | N/A            | N/A            |
  | Products    |                |                |                |
  +--------------+-----------------+-----------------+-----------------+
  | Support      | 8AM to 5PM      | 8AM to 8PM      | 8AM to 5PM      |
  | Hours        | Customer Time  | Eastern Time -  | Customer Time  |
  |              | Zone - Monday  | Monday through  | Zone - Monday  |
  |              | through Sunday  | Sunday          | through Sunday  |
  |              | (excluding U.S. | (excluding U.S. | (excluding U.S. |
  |              | national        | national        | national        |
  |              | holidays)      | holidays)      | holidays)      |
  +--------------+-----------------+-----------------+-----------------+
  | 24 X 7      | N/A (Customer  | N/A            | N/A            |
  |              | can purchase    |                |                |
  |              | platform 24 X 7 |                |                |
  |              | Single Incident |                |                |
  |              | if required)    |                |                |
  +--------------+-----------------+-----------------+-----------------+
  | Priority    | N/A            | N/A            | N/A            |
  | Handling    |                |                |                |
  +--------------+-----------------+-----------------+-----------------+
  | # of        | N/A            | N/A            | Single User,    |
  | Contacts    |                |                | Single License  |
  +--------------+-----------------+-----------------+-----------------+
  | Multivendor  | N/A            | N/A            | N/A            |
  | Coordination |                |                |                |
  +--------------+-----------------+-----------------+-----------------+
  | Monthly      | N/A            | N/A            | N/A            |
  | Activity    |                |                |                |
  | Reports      |                |                |                |
  +--------------+-----------------+-----------------+-----------------+
==TITLE: 941208 INSTALLING WARP ON VALUEPOINT 6384-199 (P60/D), ON DISK #1 HANGS WITH DISKETTE LIGHT ON AND LOGO DISPLAYED.==
DESCRIPTION OF SYMPTOMS:
    Attempting to install OS/2 Warp on ValuePoint 6384-199 (P60/D).
    Installing from diskettes.  Boot from installation diskette,
    load disk 1 when requested  disk 1 hangs with diskette light
    on and logo displayed.
    ALT-F2 shows nothing.  No driver has been loaded.
    Turned off int/ext cache and shadowing ROM did not help.
RESOLUTION:
    These ValuePoint systems came with the Flash EEPROM level
    0.13.01.AV0M and it has an AMI BIOS.  User needs to download
    VPP60FL6.DSK from the BBS in Raleigh 919-517-0001.  The
    new BIOS is 1.00.06.AV0M.
    Contact PS/VP Technical support for more informations on
    getting this new Flash EEPROM upgrade.
==TITLE: 941212 COULD NOT LOCATE VROBJ.DLL (OS/2 WARP BONUSPAK)==
DESCRIPTION OF SYMPTOMS:
    Customer is attempting to run the BonusPak Installation
    Utility (INSTALL.CMD).  The program starts up and issues
    five "1 file(s) copied" messages and then pops up an error
    box that states: " BPIU.EXE - COULD NOT LOCATE VROBJ.DLL ".
SUMMARY OF RESOLUTION:
    Somehow the customer's LIBPATH statement has been changed
    such that the ".;" (dot semicolon) has been deleted from
    the LIBPATH.  The LIBPATH statement in CONFIG.SYS should
    look similar to this: LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;
    continuing on to the end.  NOTE: C is drive where OS/2
    Warp is installed.
DETAILS OF RESOLUTION:
    If your customer is experiencing this error with the
    BonusPak Installation Utility, have the customer check
    his CONFIG.SYS file and look for the .; in the LIBPATH
    statement.  It normally should be the first entry in
    the list of subdirectories.  On a newly installed machine
    it is the first item.  It may however be located anywhere
    on the LIBPATH= line.  Ask the customer if he might have
    edited this line in his CONFIG.SYS or installed any
    applications that stated that they were going to edit
    or update CONFIG.SYS.  That will be the way to determine
    how the line might have gotten modified.  OS/2 Warp needs
    the .; in the LIBPATH to function correctly.
    A missing .; in the LIBPATH can result in all sorts of
    errors occurring with different programs of the BonusPak
    and the system in general.
==TITLE: 941207 USER MAY GET SYS3175 IN INSTALL.EXE WHILE INSTALLING WARP ON ZEOS PANTERA SYSTEM.==
;DESCRIPTION OF SYMPTOMS:
;DESCRIPTION OF SYMPTOMS:
 
User may get the following SYS3175 in Install.exe during OS/2 3.0 Installation on Zeos Pantera P90 System.
User may get the following SYS3175 in Install.exe during OS/2 3.0 Installation on Zeos Pantera P90 System.
     .  
     .
     *************** SYS3175 32-bit***************
     *************** SYS3175 32-bit***************
     A program generated an acess violation at 0004d8a9  
     A program generated an acess violation at 0004d8a9  
Line 989: Line 558:
     EBP=0000a7e8 FLG=00012246
     EBP=0000a7e8 FLG=00012246
     *************** SYS3175 32-bit End ***********
     *************** SYS3175 32-bit End ***********
;SUMMARY OF RESOLUTION:
;SUMMARY OF RESOLUTION:
Contact Zeos Technical Support for Bios Upgrade Information.
Contact Zeos Technical Support for Bios Upgrade Information.
 
;DETAILS OF RESOLUTION:
;DETAILS OF RESOLUTION:
If a system has a Flash Bios Version less than V9.0, user needs to  
If a system has a Flash Bios Version less than V9.0, user needs to upgrade his Bios to 9.0 which can be downloaded from Zeos Bulletin Board System at 612-362-1219. Once the bios is upgraded, the hardware settings for IDE drive in CMOS should be configured as following.
upgrade his Bios to 9.0 which can be downloaded from Zeos Bulletin  
  Multi Sector = Disable
Board System at 612-362-1219. Once the bios is upgraded, the hard-
  Pre Set      = Disable
ware settings for IDE drive in CMOS should be configured as  
  LBA          = Enable
following.
              Multi Sector = Disable  
              Pre Set      = Disable  
              LBA          = Enable  
For more info, please contact Zeos Technical Support.
For more info, please contact Zeos Technical Support.


==About Light Table Browsers ==
==941208 SHUTDOWN FAILS UNDER OS/2 2.11 OR WARP DUE TO LOTUS CC:MAIL BEING ON THE SYSTEM ==
DESCRIPTION OF SYMPTOMS:
 
In some cases, after installing CCMail Client on a system running WARP 3.0, the user will be unable to successfully shutdown.
 
SUMMARY OF RESOLUTION:
 
CCmail is aware of this and the 1.04 build will address this issue.
 
DETAILS OF RESOLUTION:
 
To work around this problem:
:Make sure the user either has their CCMail folder open, or places a shadow of any object within the CCMail folder on the OS/2 desktop, prior to shutdown.
 
ALSO, word from a Lotus support tech is that if the IN BOX has a shadow on the Desktop, then the problem will not occur.
 
This problem will be addressed in the version 1.04 of CCmail. The most current version of CCMail Client is 1.03 and 1.04 is scheduled to be available early 1995.
 
==941208 INSTALLING WARP ON VALUEPOINT 6384-199 (P60/D), ON DISK #1 HANGS WITH DISKETTE LIGHT ON AND LOGO DISPLAYED.==
DESCRIPTION OF SYMPTOMS:
 
Attempting to install OS/2 Warp on ValuePoint 6384-199 (P60/D).
Installing from diskettes.  Boot from installation diskette,
load disk 1 when requested  disk 1 hangs with diskette light
on and logo displayed.
ALT-F2 shows nothing.  No driver has been loaded.
Turned off int/ext cache and shadowing ROM did not help.
   
   
  o  Light Table folders provide browsers for reviewing your
RESOLUTION:
      multimedia data. There are four browsers: Audio,
 
      Video/Animation, Image and Text.
These ValuePoint systems came with the Flash EEPROM level
0.13.01.AV0M and it has an AMI BIOS.  User needs to download
VPP60FL6.DSK from the BBS in Raleigh 919-517-0001.  The
new BIOS is 1.00.06.AV0M.
Contact PS/VP Technical support for more informations on
getting this new Flash EEPROM upgrade.
 
==941209 System hangs with Adaptec 2740/2742 controller with cdrom attached.==
DESCRIPTION OF SYMPTOMS:
 
Attempting to access a CDROM attached to an Adaptec 2740/2742
scsi controller causes trap or system hang.
 
SUMMARY OF RESOLUTION:
 
Disable tagged queing for the AIC7770.ADD driver.
   
   
  o  The Audio, Video/Animation and Image browsers can be
DETAILS OF RESOLUTION:
      invoked by positioning the mouse pointer anywhere over the  
 
      SLIDE FRAME and double-clicking the left mouse button.
1. Edit the OS2 config.sys file.
      Large images may take a while to appear on your display.
 
2. Change the line
BASEDEV=AIC7770.ADD
to
BASEDEV=AIC7770.ADD /A:0 /TAG:1
 
3. Shut down system and then reboot for change to take effect.
 
==941209 WHAT IDE CD-ROMS ARE COMPATIBLE WITH OS2 Warp? AND HOW DO I MAKE THEM WORK?==
DESCRIPTION OF SYMPTOMS:
 
CDROM NOT WORKING UNDER WARP
 
SUMMARY OF RESOLUTION:
 
What Follows is a list of CD-ROMs that are known to be compatible
with Warp and how to make them work.
   
   
  o  If the mouse is located over the middle of the object (not
DETAILS OF RESOLUTION:
      the border), double-clicking the left mouse button will
      behave as it normally does in a standard OS/2 folder.
   
   
  o  The Text browser can be invoked by double-clicking on the
The IDE hard disk driver, IBM1S506.ADD, was made aware of ATAPI.
      text object.
This driver will claim all ATAPI devices and mark them as generic
devices. The IBMIDECD.FLT filter loads afterwards and scans all
drivers for generic ATAPI devices. If it locates one, it will decide
if that device is a CDROM.
   
   
  o  The browsers will work with any file type supported by the  
Note:  In addition to IBM1S506.ADD and IBMIDECD.FLT, all CD-ROM
      OS/2 Multimedia system. See your OS/2 documentation for
in the table below require the OS2CDROM.DMD and CDFS.IFS device
      more information on supported file formats.
These are added automatically when the selective install is done.
   
   
==Creating a new Light Table folder==
CDROM.
Light Table folders are created in the same manner as
standard OS/2 folders.  After installing the Multimedia
Viewer, open the Templates folder and locate the Light
Table template.  Drag/Drop the Light Table Template to the
desired location on your desktop.
   
   
==Adding New Files to your Light Table==
An IDE CDROM cannot be a master while a hard drive is being a slave.
You cannot use the IBMINT13.I13 for an IDE CDROM.
   
   
      The preferred method of adding multimedia data objects to
{|class="wikitable"
      a light table folder is to create a "Light Table
!Manufacturer||Model||Notes
      Reference".  Follow the steps below.
|-
|Mitsumi||FX001DE||1
|-
|NEC||CDR-250||
|-
| ||CDR-260||2
|-
| ||NEC 2vi||
|-
|Sony||55E||1
|-
| ||55D||1
|-
|Panasonic||571||
|-
|Wearnes||CDD-120|
|}
    Notes:
   
   
  o  Find the data object you wish to use by opening its folder.
    1. The Mitsumi and Sony cdroms may have problems because they are not
        ATAPI 1.2 compliant. This should be fixed with updated drivers.
   
   
  o  Click the right mouse button on the data object to bring
    2. NEC 260 cdroms that ship with some Gateway systems adhere to the  
      up the object's popup menu.
        1.7 spec instead of 1.2. For these cdroms, the BASEDEV=IBM1S506. A
        line in the OS2 config.sys file has to be edited as follows:
   
   
  o  Select "Create LT Reference" from the popup menu.
                BASEDEV=IBM1S506.ADD /A:x /U:y /ATAPI
   
   
  o  Select the Light Table folder in which you want the data
        The /A switch refers to the adapter number that the cdrom
      object to appear. Only Light Table folders can be
        is attached to. The /U option references the unit or device
      selected. A miniature slide for the data file should
        number on a particular adapter. The /ATAPI parameter
      now be visible in your Light Table folder.
        enables ATA Packet Interface protocol for the NEC 260. If the
        cdrom is attached to the second IDE port or adapter in a
        system and is the only device on the adapter you would
        enter:
                BASEDEV=IBM1S506.ADD /A:1 /U:0 /ATAPI
   
   
== Additional Light Table Reference Object Tips ==
==941212 COULD NOT LOCATE VROBJ.DLL (OS/2 WARP BONUSPAK)==  
DESCRIPTION OF SYMPTOMS:
 
Customer is attempting to run the BonusPak Installation
Utility (INSTALL.CMD).  The program starts up and issues
five "1 file(s) copied" messages and then pops up an error
box that states: " BPIU.EXE - COULD NOT LOCATE VROBJ.DLL ".
 
SUMMARY OF RESOLUTION:
   
   
  o  Light Table Reference objects are similar to Shadow
Somehow the customer's LIBPATH statement has been changed
      objects. They are a reference to another object or file.
such that the ".;" (dot semicolon) has been deleted from
      Unlike Shadow objects:
the LIBPATH.  The LIBPATH statement in CONFIG.SYS should
look similar to this: LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;
continuing on to the end. NOTE: C is drive where OS/2
Warp is installed.
   
   
      -  References provide storage for slide images.
DETAILS OF RESOLUTION:
   
   
      -  References are preserved when the parent object is  
If your customer is experiencing this error with the
          not present.
BonusPak Installation Utility, have the customer check
his CONFIG.SYS file and look for the .; in the LIBPATH
statement.  It normally should be the first entry in
the list of subdirectories.  On a newly installed machine
it is the first item.  It may however be located anywhere
on the LIBPATH= line.  Ask the customer if he might have
edited this line in his CONFIG.SYS or installed any
applications that stated that they were going to edit
or update CONFIG.SYS.  That will be the way to determine
how the line might have gotten modified.  OS/2 Warp needs
the .; in the LIBPATH to function correctly.
   
   
      These features allow Light Table References to display
A missing .; in the LIBPATH can result in all sorts of
      slides in a Light Table folder even when the parent object
errors occurring with different programs of the BonusPak
      is removed.  For example, if a CD-ROM containing an image
and the system in general.
      is removed, the image slide will remain in the Light
 
      Table.
==941213 FLOPPY DOES NOT WORK IN WARP ON NCR 3333 SYS0049 ERROR==
;DESCRIPTION OF SYMPTOMS:
  o  When selecting multiple objects to create Light Table
    Floppy drive does not work in WARP.
      References, do not mix .BMP files or .ICO files with other
    SYS0049 Error When accessing the A (Floppy) Drive
      data file objects.  You can select all .BMP files as one
    Problems with the Floppy drive on the NCR 3333 DX2/66
      group, then create Light Table References for these
 
      selected objects.  Select all .ICO files as another group
;SUMMARY OF RESOLUTION:
      to create Light Table References.  Then select all the rest
    Have A T & T / NCR replace the system board.
      of the objects to create Light Table References.
 
;DETAILS OF RESOLUTION:
  o  When you double click the center of objects in the Light
    Replace the system board. NCR acknowledges that this is a hardware  e
      Table, the OS/2 Workplace Shell will launch any
    problem with the system board (bad IC pack on the system board). This proble
      application in OS/2 that has an association with that
    occurs on many multi-tasking operating systems including OS/2, NT,  d Unix.
      filetype.  For example if you double click on an OS/2 .BMP
    and Unix. Call A T & T at 800 262-7782 (as of Dec 1994) and ask them  the
      file, you will launch the OS/2 Icon Editor.  A file type
    to replace the system board due to FLEX DRIVE problems. This is AT&T / NCR Defect Number 86647.
      will be associated to any application that supports it if
 
      the application has set up the association.
==941214 COREL DRAW! 3.0 WON'T START UNDER OS/2; GETS ERROR COREL DRAW 3 SECTION DRAWDIR=KEY NOT FOUND IN WIN.INI==
DESCRIPTION OF SYMPTOMS:
==Installation Notes==
When trying to run Corel Draw! 3.0 for Windows under OS/2 the user
      The Multimedia Viewer is installed on the same drive as
cannot run the application and gets error, "Corel Draw 3 section
      the OS/2 Multimedia \MMOS2 directory, and requires about
drawdir=key not found in WIN.INI." Corel Draw! cannot be run.
      1.3 MB of disk space.  If this drive is the one that is
 
      used by the OS/2 swapper, this reduces the amount of
SUMMARY OF RESOLUTION:
      swapper space available for the system.  In this case, you
1.  Modify WIN.INI file to address missing entry.
      may want to change the drive used for the OS/2 swapper to
 
      one containing more space.  Refer to the SWAPPATH
2.  It may be possible to simply modify the PATH statement in the
      statement in the Command Reference information (in the
OS/2 AUTOEXEC.BAT file to include the Corel Draw directory so
      Information folder on your desktop) for more details about
that the CORELDRW.INI file can be found.
      determining and changing the location of the OS/2 swapper
 
      file.
DETAILS OF RESOLUTION:
    1.  Edit the WIN.INI file and add the following:
==TRADEMARK INFORMATION ==
 
            {CorelDraw3.
      IBM and OS/2 are registered trademarks of
            drawdir=C:\CorelDrw
      International Business Machines Corporation.
 
        NOTE: CorelDraw3 is enclosed in square brackets.
README FILE FOR OS/2 3.0 Utility Diskettes
              Also the directory may be modified as needed.
_____________________________________________
 
    2.  The user may also be able to modify the AUTOEXEC.BAT file of
August 1994
        OS/2 so that the PATH statement includes whatever directory
        Corel Draw! 3.0 is located in, such as C:\CorelDrw as
This file contains additional information about
        above
using the Utility Diskettes.
 
==941216 OS/2 WARP ENHANCED IDE SUPPORT==
You can use the Utility Diskettes to:
                                                    SYSTEMS WITH
                              NATIVE SUPPORT      TRANSLATED BIOS*
o  Start OS/2* 3.0 from diskettes
ENHANCED IDE FEATURE
                                DOS    OS/2          DOS    OS/2
o  Back up and restore your system
-----------------------------------------------------------------
DRIVES > 1024 CYL (> 528 MB)
o  Check the hard disk for errors or problems
 
BOOT PARTITIONS < 1024 CYL    YES    YES            YES    YES
o  Format a diskette or the hard disk
 
ACCESS DISK PAST 1024 CYL      NO    NO            YES    YES
USING BACKUP AND RESTORE
 
LOGICAL BLOCK ADDRESSING      NO    YES            NO    YES
The BACKUP and RESTORE files on Utility Diskette 3
                              with parameters    with parameters
allow you to back up and restore your entire hard disk.
for performance              /A:0 /U:0 /LBA      /A:0 /U:0
BACKING UP YOUR SYSTEM
You can use the BACKUP file on Utility Diskette 3
to back up your system.  BACKUP copies the
files from the hard disk to diskettes.  A complete
backup of your  system requires about
50 blank formatted, high-density (2MB) diskettes for OS/2
and based on other software installed an additional
diskette for each 1.44 megabytes of files.
Make backup diskettes of your system
as it was originally shipped.  Backup diskettes
allow you to restore your system, if the hard disk
is ever damaged.
For informatoin on using the backup program refer to
your Users Guide or Concise Publication.
RESTORING YOUR SYSTEM
Use the RESTORE file on Utility Diskette 3 to
restore your system.  RESTORE copies files from
the backup diskettes to your hard disk.
If you ever need to restore the backup diskettes
to your hard disk, make sure you know if your hard
disk has a formatted partition.  If the hard disk
(drive C) has a formatted partition, follow the
instructions for the restore utility described in
the OS/2 Users Guide or Concise Publication.
If the hard disk does not have a formatted
partition, create a partition and format the
partition before proceeding with the restore
procedure described in the booklet for your
system.  Use FDISK to create a partition and
FORMAT to format the partition.  The FDISK
and FORMAT command files are on Utility
Diskette 3.
==TRADEMARKS AND SERVICE MARKS ==
Terms denoted by a single asterisk in this file
(*) are trademarks of the IBM Corporation in the
United States and/or other countries.  These terms
include:
  OS/2
IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR
IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES
OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE
INFORMATION IN THIS DOCUMENT.  BY FURNISHING THIS
DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED
PATENTS OR COPYRIGHTS.
Copyright IBM Corporation, 1993, all rights
reserved.
                  IBM Internet Connection for OS/2
    Welcome to the IBM Internet Connection for OS/2.  This README
    contains the latest information available.  For an overview of
    this package prior to installation, refer to the BonusPak User's
    Guide.  After installation, you can get an introduction and
    information on how to use these applications by opening the IBM
    Internet Connection for OS/2 folder and clicking on the
    Introduction to the IBM Internet Connection icon.
    IBM OS/2 World Wide Web client software available
    -------------------------------------------------
    Once you have connected to the Internet with this package, you
    can download IBM's OS/2 World Wide Web client, WebExplorer.
    Initially this will be a pre-release version.  The final version
    will also be available for download along with any updates to
    other applications in this package.  To access these updates,
    open the IBM Internet Connection for OS/2 folder and click on the
    Retrieve software updates icon.  Click on the help button for
 

Latest revision as of 22:25, 2 March 2025

Article Info
Author Irv Spalten
Date 1994-12-12
OS Version OS/2 Warp 3
Companion File N/A
Source

Information current as of December 12, 1994

These are solutions to problems encountered in OS/2 Warp.

941026 THE SWAPPER FILE IN WARP

DESCRIPTION OF SYMPTOMS:

The swapper file is larger in WARP than in previous releases of OS2.

SUMMARY OF RESOLUTION:

This is normal.

DETAILS OF RESOLUTION:

This is normal. The most significant change that has been made is how system DLL's get loaded and what is now valid data for swapping. System DLL's include:

    DISPLAY          SOM          PMMERGE      PMWP
    DOSCALL1         PMATM        PMMLE
    IBMDEV32         PMCTLS       PMSPL 
    IBMVGA32         PMGPI        PMVIOP

In the previous versions of OS/2, dll code was never copied to the swapper file. In WARP, code for system dll's can be written to the swapper file and, in adition, during boot, PMMERGE, DOSCALL1, PMGPI, PMWP and PMVIOP will be swapped out. This means that there will be an overall increase in swapper size. This was done to increase overall system perfomance.

941027 INSTALLATION OF WARP HANG ON DISK #1 WHEN INSTALL ON GATEWAY COMPUTERS

DESCRIPTION OF SYMPTOMS

Hang on DISK #1 when installing WARP on Gateway machines.

RESOLUTION

If you are having this problem, please check the level of BIOS on your system. If you have a Gateway 1.00.03.AF1 BIOS, then you need to update your BIOS (see the README). A fix is available from Gateway.

941027 4030VL, Promise VLB Diskcaching Card IDE controller failed installing Warp.

DESCRIPTION OF SYMPTOMS:

Even with cache disabled, the motherboard bios for disk I/O and all ide drives above 0 and 1 disconnected a complete failure with the repeated message that drive C is not available and so forth all the way thru D and the logical drive partitions on both physical drives. Note: the above is an example if the user has 2 physical drives connected to this Promise card.

RESOLUTION:

Get a newer driver available from the Promise BBS. The file is PTI1S506.ADD. When using this, the IBM1S506.ADD must be remmed out first. The older driver for DV4030VLIDE will not work.

941028 Problem installing "Internet Connection for OS/2" portion of the Warp BonusPack from CDROM on Mitsumi CDROM drives

DESCRIPTION OF SYMPTOMS

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.

SUMMARY OF RESOLUTION

The user has the following options:

1.) 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.

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.) 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.

4.) If none of the above suggestions work, recommend that the user obtain a replacement BonusPack CDROM

DETAILS OF RESOLUTION

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.

941103 INSTALLING S3964 DRIVERS ON WARP OS/2 VERSION 3.0 USING S3'S DRIVERS (THOSE WRITTEN BY S3 CORP.)

DESCRIPTION OF SYMPTOMS:

Problems installing the S3 drivers for the S3 964 chip on system with OS/2 v3.0

  1. The install does not finish
  2. The install hangs

SUMMARY OF RESOLUTION:

  1. Edit the S3inst.cmd file
  2. Change all references to x:\os2 to x:\os2\boot.
         (X: = drive where os2 resides)

The drivers in original format will not install because the reference the Os2 directory. Os2 v 3.0 installs the drivers into the Os2\Boot directory.

DETAILS OF RESOLUTION:

  1. Edit the S3INST.CMD file by:
    a. Place the S3 driver diskette into the disk drive.
    b. Change to the disk drive
    c. Pull S3INST.CMD into an editor
  2. Change the reference from X:\OS2 TO X:\OS2\BOOT ('X' = drive where OS/2 resides)

Note: The drivers in the original format will not install since reference is to the \OS2 directory. OS/2 v3.0 installs drivers into the \OS2\BOOT directory

941114 Configuring the NEC 260 IDE cdrom under OS2 Warp

DESCRIPTION OF SYMPTOMS

A NEC 260 IDE cdrom is not being recognized by OS2 Warp.

SUMMARY OF RESOLUTION

Make sure the proper drivers are loading in config.sys and that the necessary files are located in the proper directories.

DETAILS OF RESOLUTION

If you have already installed OS2 Warp, and are trying to get the cdrom recognized, follow these instructions:

  1. Go to the OS2 Selective Install utility. From the list of cdrom's, select the NEC 260. Click OK. At the System Configuration window, click OK again. At the Setup and Installation window, select the Install button.
  2. Insert the OS2 diskette when prompted.
  3. Edit the OS2 config.sys in the root directory of the hard drive. Find the line:
    BASEDEV=IBM1S506.ADD
        Add switches to this line so that it reads:

                          BASEDEV=IBM1S506.ADD /A:x /U:y /ATAPI

        The /A switch refers to the adapter number that the cdrom 
        is attached to. The /U option references the unit or device 
        number on a particular adapter. The /ATAPI parameter 
        enables ATA Packet Interface protocol for the NEC 260. If the 
        cdrom is attached to the second IDE port or adapter in a 
        system and is the only device on the adapter, you would enter 

                          BASEDEV=IBM1S506.ADD /A:1 /U:0 /ATAPI

        in the config.sys. If the cdrom is configured as a slave, or sec 
        device, you would specify /U:1. The config.sys should also conta 
        the statements:

                           BASEDEV=IBMIDECD.FLT
                           DEVICE=C:\OS2\BOOT\OS2CDROM.DMD
                           IFS=C:\OS2\BOOT\CDFS.IFS

         These should have been added by the Selective Install program.

         If you are trying to install Warp from the NEC 260 cdrom,
         simply configure the BASEDEV=IBM1S506.ADD line per above.
         If you find that OS2 still does not recognize the cdrom,
         make sure that the /A and /U parameters are specified

941115 Warp TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT

DESCRIPTION OF SYMPTOMS:

When installing TCPIP Version 2.0 and The Internet Connection Kit you will receive an error message that the products are not supported when running TOGETHER. It will install, but there are several problems and certain features will not work.

SUMMARY OF RESOLUTION:

Running TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT together under WARP is NOT supported.

DETAILS OF RESOLUTION:

Running TCPIP VERSION 2.0 AND THE INTERNET CONNECTION KIT together under WARP is NOT supported.

941115 RUNNING WEB EXPLORER UNDER WARP

DESCRIPTION OF SYMPTOMS:

You can run Web Explorer under WARP version 3.0 as well as TCP-IP version 2.0 with the base kit service pack for TCPIP 2.0.

SUMMARY OF RESOLUTION:

The customer will need obtain support from the Internet.

DETAILS OF RESOLUTION:

If the customer is running Web Explorer they must obtain support from the internet.

The support news group on the internet newsgroup is:

comp.os.os2.networking.tcp-ip

941115 CHANGES MADE BY WARP TO WINDOWS FILES

DESCRIPTION OF SYMPTOMS:

Changes to several Windows files occur during installation of OS/2 3.0 Warp

SUMMARY OF RESOLUTION:

The Following Windows files are Modified during WARP installation:

WIN.INI
SYSTEM.INI
WIN.COM
CONTROL.INI
PROGMAN.INI
SETUP.INF
CONTROL.INF

DETAILS OF RESOLUTION:

Changes to the following files are as follows:

WIN.INI

.Windows.
if no printer is defined in WINDOWS, Warp will 
insert GENERIC / TEXT ONLY in the DEVICE= statement.
.Desktop.
Adds ICON SPACING=100

note: this statement may or may not appear in this 
      section. If it does not, Warp will insert it 

.Ports.
         Adds .OS2 ports 

.Pscript.
This section is created and the following statements 
are added:
EXTERNAL PRINTERS=6
PRINTER1=40291760
PRINTER2=40291730
PRINTER3=40293930
PRINTER4=40293960
PRINTER5=IBM17521
PRINTER6=IBM39521

.Device.
This section is created and the following statement 
is inserted:
GENERIC/TEXT ONLY TTY, LPT1:

.Printer Ports.
This section is created and the following statement 
is inserted:
GENERIC / TEXT ONLY=TTY,LPT1:,15,45

SYSTEM.INI

.Boot.
LANGUAGE.DLL= is modified to =LANGENG.DLL (to ensure english)
SYSTEM.DRV= is modified to =ATMSYS.DRV
MAVDMApps= is added 
OS2MOUSE.DRV=MOUSE.DRV is added 
ATM.SYSTEM.DRV=SYSTEM.DRV is added 
USEOS2SHIELD=1 is added 
OS2SHIELD=WINSHELD.EXE

.Keyboard.
KEYBOARD.DLL= is modofied to =KBDUS.DLL

.386Enh.
MAY change the path in the PAGING FILE= statement 
Changes the MAXPAGINGFILESIZE= statement 

.Timer.drv.
This section is created and the following statements are 
inserted:
Max386Res=10
Max286Res=10

CONTROL.INI

.Installed.
This section is created and the following statements 
are inserted:
3.1=YES
HPPCL5A.DRV=yes
FINSTALL.DLL=YES
FINSTALL.HLP=YES
HPPCL5A.HLP=YES
HPPCL50P.HLP=YES
note: the reference to the HP universal print drivers are 
      due to an HP LaserJet being selected during install.

.Function.
This section is created and the following statement is 
inserted:
SETTINGS=COLORS, FONTS, PORTS, MOUSE, DESTOP, PRINTERS 
         INTERNATIONAL, SOUND, NETWORK 

PROGMAN.INI

.Settings.
display.drv=<installed resolution> is inserted 

SETUP.INF

.oemdisks.
A =. ,"IBM OS/2 Printer Driver Diskette 1","PMDD 1"
B =. ,"IBM OS/2 Printer Driver Diskette 2","PMDD 2"
C =. ,"IBM OS/2 Printer Driver Diskette 3","PMDD 3"

941121 TRAP0003 DISK #1 IBM1FLPY.ADD WARP OS/2. CS:EIP=0538:00001a21 CSLIM=000027d7.

DESCRIPTION OF SYMPTOMS:

Installing WARP disk #1 failed with TRAP0003 on the following values: CS:EIP=0538:00001a21 CSLIM=000027d7.

SUMMARY OF RESOLUTION:

On the system setup bios, check the SETUP for the floppy drive setup. Make sure that the floppy drive is setup correctly. Example: If user has 1.44mb (3 1/2") drive, make sure the setup reflects 1.44mb setup instead of 1.2mb (5 1/4").

941121 INSTALLING WARP, GETTING SYS0045 ON WINDOWS DISK #1

DESCRIPTION OF SYMPTOMS

Installing OS/ WARP passed the first phase and onto the second phase of the installation, when asks to insert the WINDOWS DISK #1, will received a " SYS0045 sector can't be found ... " If going into OS/2 and DIR on the WINDOWS DISKS, it is ok, but if trying to copy, xcopy any files from the WINDOWS DISKS to the hardfile, result the same error SYS0045 message.

SUMMARY OF RESOLUTION

User has changed the floppy drives around and did not update the CMOS to reflects the changes.

DETAILS OF RESOLUTION

User must go into the system CMOS and make sure the floppy drives are setup correctly.

Example: If changed the 1.44mb drive from B: to A:, and the 1.2mb drive from A: to B:, on the Setup on the CMOS should reflect that 1.44mb as an A: drive and 1.2mb as an B: drive.

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

DESCRIPTION OF SYMPTOMS:

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

SUMMARY OF RESOLUTION:

Ensure the MOUSE.INI file has a type specified

DETAILS OF RESOLUTION:

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

941122 INSTALLING OS/2 WARP, INTERNAL CDROM DRIVE CONNECTED TO A SOUNDCARD DIRECTLY (NOT A SEPARATE CONTROLLER CARD).

DESCRIPTION OF SYMPTOMS:

Not recognizing cdrom. OS2CDROM.DMD not found.

RESOLUTION:

This is a hardware related problem. User needs to do the following: On the back of the cdrom drive is a jumper which controls the bus device number. OS/2 install requires it to be on 0 (zero). Most sound board manufacturers leave it at the factory default of 1. If it is anything other than 0, the install disk #1 will not load the driver " OS2CDROM.DMD " and will stop installation with a red screen saying it can't find the cdrom.

941123 INSTALLING WARP ON A SYSTEM WITH FUTURE DOMAIN 1680, FIRST PHASE HANG WITH A BLINKING CURSOR. NO LOGO ON THE FIRST REBOOT.

DESCRIPTION OF SYMPTOMS:

Installing WARP on a system with Future Domain 1680 SCSI controller and Toshiba 3401b CDROM, hang after the first reboot with a blinking cursor on the top left hand corner. No logo, just a black screen with blinking cursor. This is on a 1.5gb Maxtor hardfile.

SUMMARY OF RESOLUTION:

User has low-level formatted the hardfile under the Future Domain utilities, but did not partition the drive and high-level format under this utilities. The Maxtor drive cylinders set is incorrect, showing 816 instead of actual 1014 cylinders. The hardfile was NOT correctly defined previously therefore causing this problem.

DETAILS OF RESOLUTION:

Make sure the hardfile is correctly define and format under the Future Domain Utilities to avoid this problem.

941123 INSTALLING WARP ON A SYSTEM WITH CDROM (TOSHIBA) CONNECTED TO AN ADAPTEC 1542C, GETTING A RED SCREEN NO CDROM DEVICE SUPPORT FOUND.

DESCRIPTION OF SYMPTOMS:

Red screen on DISK #1, message no cdrom device support found.

RESOLUTION:

Under the Adaptec setting option (Ctrl+A), disable the FAST SCSI and Synchronize option. This will enabled OS/2 WARP install DISK #1 to recognize the cdrom.

Note: The system has also a SoundBlaster card, but the cdrom (Toshiba) is connected to the Adaptec 1542C SCSI controller.

941129 C0000005 ON DISK #1 INSTALLATION OF WARP CS:EIP = 013b : 00000ced CSLIM = 000025ab

DESCRIPTION OF SYMPTOMS:

Installation of WARP, on Disk 1 received the following error: A program in this session encountered a problem and cannot continue.

c0000005
P1 =00000000 P2 =ffffffff P3 =xxxxxxxx P4 =xxxxxxxx
EAX=00000002 EBX=ffe4a814 ECX=00000041 EDX=ffe28c44
ESI=ffe4000a EDI=ff3f0008
DS=03cb  DSACC=00f3  DSLIM=000007ff
ES=0130  ESACC=00f3  ESLIM=00005133
FS=0000  FSACC=****  FSLIM=********
GS=0000  GSACC=****  GSLIM=********
CS:EIP=013b:00000ced CSACC=00fb  CSLIM=000025ab
SS:EIP=0017:00000fc6 SSACC=00f3  SSLIM=00000fff
EBP=00000433 FLG=00013202

SUMMARY OF RESOLUTION:

Check the CONFIG.SYS, user has edited this file and instead of putting " REM " for remarks out the statement, user put a non- alphabet characters. For example, instead of the following: REM basedev=ibm1s506.add user has put

;basedev=ibm1s506.add  (a semi-colon " ; ")

This above will result the c0000005 error on disk #1.

DETAILS OF RESOLUTION:

Make sure the user does not use any non alphabet characters for any statements on the config.sys. Under OS/2, everytime a statement needs to be REMarks out, user REM instead of ";" or non alphabet characters.

941129 WARP PACKAGE UPDATE - HOW TO FIND OUT WHICH WARP PACKAGE THE CUSTOMER RECEIVED

DESCRIPTION OF SYMPTOMS

How to tell which WARP Package the customer is running.

SUMMARY OF RESOLUTION

Check the manufactured packages. The SYSINST1.EXE file has been updated.

DETAILS OF RESOLUTION

The only file that was changed in the updated WARP Package is SYSINST1.EXE. This file is located on Disk 1 or CD Rom 1 and is installed to:

X:\OS2\INSTALL\BOOTDISK\SYSINST1.EXE

The old file size for SYSINST1.EXE is 4992 bytes, dated 10-08-94. The new file size for SYSINST1.EXE is 4960 bytes, dated 10-25-94.


The following should be used to distinguish the original GA version of WARP from the updated packages, or from newly manufactured packages.

  1. 16-Digit Code on Bottom of WARP Box (1st 6 Digits are Date of Mfg)
    • If Down-Level (not reworked) will have date prior to 10/29/94
    • If Reworked, will have Original Code w/date prior to 10/29/94 PLUS Additional 16-Digit Code that will reflect date of rework
    • Single 16-Digit Code w/date After 10/29, reflects newly Manufactured Product, w/revised code.
  2. Shipping Carton of any "REWORKED" Product will have a single WHITE STICKER (no text) on outside of Box. White sticker will be visible thru pallet.
  3. Diskette Label of Diskette 1 has revised Part Number (P/N):
    83G8658 (for Diskette Version)
    83G8661 (for CD-ROM Version)

941130 TRAP000E WITH CS:EIP 0160:FFF6EFBE

DESCRIPTION OF SYMPTOMS:

Customer receives a Trap000e with cs:eip 0160:FFF6EFBE when running laps WR06000 and/or lan server IP07000. The function name which is failing is _VMGetSem.

SUMMARY OF RESOLUTION:

Customer must upgrade to the latest csd's for Laps and Lan server. (WR07045 and IP07045)

DETAILS OF RESOLUTION:

If a customer receives a Trap000E with CS:EIP 0160:FFF6EFBE they must upgrade their Laps to WR07045 and Lan Server to IP07045.

NOTE: This may not necessarily pertain to Laps and Lan Server. If the customer is running any other Product such as Novell, other Lan software, or specific drivers make sure they are updated to the latest version.

941201 Philips cdrom causes boot problem if /m parameter used

DESCRIPTION OF SYMPTOMS:

After setting the number of 2500 byte CD frame buffers to a value greater than the default value, OS2 will not boot. The default value is 16, the maximum 26, and the minimum 8. If customer is loading the LMS205.ADD driver, the line in config.sys would read

BASEDEV=LMS205.ADD /m:26

to specify 26 2500 byte CD frame buffers.

With the Philips 206 cdrom, the line would read

BASEDEV=LMS206.ADD /m:

SUMMARY OF RESOLUTION:

Change the number of CD frame buffers back to the default value.

DETAILS OF RESOLUTION:

Please follow these instructions:

  1. Bring up the OS2 config.sys in an editor.
  2. Check the config.sys for the statements
    BASEDEV=LMS205.ADD /m:26
  3. Remove the /m:26 so the line reads
    BASEDEV=LMS205.ADD
  4. Save the file, shutdown and reboot for the changes to take effect.

941205 GENERAL PROBLEMS ON INSTALLATION OF WARP, MAINTENANCE DESKTOP OR BEFORE THE FINAL REBOOT

DESCRIPTION OF SYMPTOMS:

  1. Customer receives sys3175 in os2mm.dll (PJ16290) on first reboot or Maintenance Desktop.
  2. Customer receives sys3175 in unpack2.exe, when continuing installation through the maintenance desktop on any diskette.
  3. OS2 is unable to operate your hard disk or your diskette drive.
  4. System hangs on maintenance desktop.
  5. System beeps on diskette #7 when asking for the diskette.

RESOLUTION:

Remark out the basedev=xxxxxxx.add from config.sys on the harddrive except ibmint13.i13 and ibm%flpy.add and the cdrom controller device driver (Where xxxxxx can be any character and % is replaced by 2 for microchannel system and a 1 if any other system). Also refer customer for possible 174 in Users Guide to OS/2 book additional explanation and actions. If customer has Ethernet Card (NE2000 Compatible), ask to customer to remove it (PJ15955).

941207 WARP ERROR MESSAGE "DRIVE X NOT READY PRESS ANY KEY"

DESCRIPTION OF SYMPTOMS:

CUSTOMERS USING THE BOOT MANAGER FEATURE UNDER OS/2 WARP MAY GET THE ERROR MESSAGE "DRIVE 1 NOT READY PRESS ANY KEY" AND THE SYSTEM BOOTS NORMALLY. OTHER DRIVES NUMBERS MAY ALSO BE REPORTED AS NOT READY. THIS IS MOST PREVALENT ON COMPUTERS THAT UTILIZE A SCSI HOST ADAPTER.

SUMMARY OF RESOLUTION:

THE CUSTOMER SHOULD CHECK THE HARDWARE SETTINGS OF ALL THE DRIVES IN HIS SYSTEM. ON SYSTEMS WITH SCSI HOST ADAPTERS, BE CERTAIN THAT ONLY BOOTABLE DRIVES HAVE A SCSI ID OF 0 OR 1. USING FDISK FROM A PREVIOUS VERSION OF OS/2 TO INSTALL THE BOOTMANAGER WILL CIRCUMVENT THE MESSAGE.

DETAILS OF RESOLUTION:

THE ERROR MESSAGE APPEARING IS THE RESULT OF ADDITIONAL MESSAGEING THAT WAS ADDED TO ALERT A USER THAT AN EXTERNAL DRIVE MAY NOT BE POWERED ON. ONE OF THE REASONS THAT IT APPEARS FOR WARP USERS WITHOUT EXTERNAL DRIVES MAY BE A NON STANDARD IMPLENTATION OF THE BIOS IN THE USERS SCSI CARD. USING THE FDISK PROGRAM FROM A PREVIOUS VERSION OF OS/2 WILL STOP THE ERROR MESSAGE FROM APPEARING. FDISK.COM IS LOCATED ON DISK 1 OF MOST VERSIONS OF OS/2 INSTALLATION DISKETTES, IT IS ALSO IN THE \OS2SE21\DISK_2 DIRECTORY OF MOST OS/2 CDROMS.

941207 IPE 0160:FFFBA0FC - 000D:000680FC, 1163, 7019 ON DISK 1 INTERNAL REVISION 8.162 94/09/19

DESCRIPTION OF SYMPTOMS:

Installing WARP on Disk #1 when the user replaced the IBMKBD.SYS with the size of 29,525, will get the following IPE.

*************** IPE 16/32-bit *************************
  THE SYSTEM DETECTED AN INTERNAL PROCESSING 
   ERROR AT LOCATION # 0160:fffba0fc - 000d:000680fc
   1163, 7019 
  048600b4 
  INTERNAL REVISION  8.162      94/09/19
*********** end IPE 16/32-bit ************************

RESOLUTION:

User has downloaded the wrong IBMKBD.SYS file. The file size should be 4,677 and dated 7/30/94. Note: this file is the temporarily fix for PJ16077

941207 USER MAY GET SYS3175 IN INSTALL.EXE WHILE INSTALLING WARP ON ZEOS PANTERA SYSTEM.

DESCRIPTION OF SYMPTOMS

User may get the following SYS3175 in Install.exe during OS/2 3.0 Installation on Zeos Pantera P90 System.

    .
    *************** SYS3175 32-bit***************
    A program generated an acess violation at 0004d8a9 
    install.exe 0004:0000d8a9
    P1=00000008 P2=000000a0 P3=xxxxxxxx P4=xxxxxxxx  EAX=00000000
    EBX=00000004 ECX=00000005 EDX=bed80127
    ESI=00000d22 EDI=00005628
    DS=008f  DSACC=00f3  DSLIM=0000d12f
    ES=0127  ESACC=00f3 ESLIM=00000d22
    FS=150b  FSACC=00f3  FSLIM=00000030
    GS=0000 GSACC=****  GSLIM=********
    CS:EIP=0027:0000d8a9 CSACC=00fb CSLIM=0000daa9
    SS:EIP=008f:0000a7d2 SSACC=00f3  SSLIM=0000d12f
    EBP=0000a7e8 FLG=00012246
    *************** SYS3175 32-bit End ***********
SUMMARY OF RESOLUTION

Contact Zeos Technical Support for Bios Upgrade Information.

DETAILS OF RESOLUTION

If a system has a Flash Bios Version less than V9.0, user needs to upgrade his Bios to 9.0 which can be downloaded from Zeos Bulletin Board System at 612-362-1219. Once the bios is upgraded, the hardware settings for IDE drive in CMOS should be configured as following.

 Multi Sector = Disable
 Pre Set      = Disable
 LBA          = Enable

For more info, please contact Zeos Technical Support.

941208 SHUTDOWN FAILS UNDER OS/2 2.11 OR WARP DUE TO LOTUS CC:MAIL BEING ON THE SYSTEM

DESCRIPTION OF SYMPTOMS:

In some cases, after installing CCMail Client on a system running WARP 3.0, the user will be unable to successfully shutdown.

SUMMARY OF RESOLUTION:

CCmail is aware of this and the 1.04 build will address this issue.

DETAILS OF RESOLUTION:

To work around this problem:

Make sure the user either has their CCMail folder open, or places a shadow of any object within the CCMail folder on the OS/2 desktop, prior to shutdown.

ALSO, word from a Lotus support tech is that if the IN BOX has a shadow on the Desktop, then the problem will not occur.

This problem will be addressed in the version 1.04 of CCmail. The most current version of CCMail Client is 1.03 and 1.04 is scheduled to be available early 1995.

941208 INSTALLING WARP ON VALUEPOINT 6384-199 (P60/D), ON DISK #1 HANGS WITH DISKETTE LIGHT ON AND LOGO DISPLAYED.

DESCRIPTION OF SYMPTOMS:

Attempting to install OS/2 Warp on ValuePoint 6384-199 (P60/D). Installing from diskettes. Boot from installation diskette, load disk 1 when requested disk 1 hangs with diskette light on and logo displayed. ALT-F2 shows nothing. No driver has been loaded. Turned off int/ext cache and shadowing ROM did not help.

RESOLUTION:

These ValuePoint systems came with the Flash EEPROM level 0.13.01.AV0M and it has an AMI BIOS. User needs to download VPP60FL6.DSK from the BBS in Raleigh 919-517-0001. The new BIOS is 1.00.06.AV0M. Contact PS/VP Technical support for more informations on getting this new Flash EEPROM upgrade.

941209 System hangs with Adaptec 2740/2742 controller with cdrom attached.

DESCRIPTION OF SYMPTOMS:

Attempting to access a CDROM attached to an Adaptec 2740/2742 scsi controller causes trap or system hang.

SUMMARY OF RESOLUTION:

Disable tagged queing for the AIC7770.ADD driver.

DETAILS OF RESOLUTION:

1. Edit the OS2 config.sys file.

2. Change the line

BASEDEV=AIC7770.ADD

to

BASEDEV=AIC7770.ADD /A:0 /TAG:1

3. Shut down system and then reboot for change to take effect.

941209 WHAT IDE CD-ROMS ARE COMPATIBLE WITH OS2 Warp? AND HOW DO I MAKE THEM WORK?

DESCRIPTION OF SYMPTOMS:

CDROM NOT WORKING UNDER WARP

SUMMARY OF RESOLUTION:

What Follows is a list of CD-ROMs that are known to be compatible with Warp and how to make them work.

DETAILS OF RESOLUTION:

The IDE hard disk driver, IBM1S506.ADD, was made aware of ATAPI. This driver will claim all ATAPI devices and mark them as generic devices. The IBMIDECD.FLT filter loads afterwards and scans all drivers for generic ATAPI devices. If it locates one, it will decide if that device is a CDROM.

Note: In addition to IBM1S506.ADD and IBMIDECD.FLT, all CD-ROM in the table below require the OS2CDROM.DMD and CDFS.IFS device These are added automatically when the selective install is done.

CDROM.

An IDE CDROM cannot be a master while a hard drive is being a slave. You cannot use the IBMINT13.I13 for an IDE CDROM.

Manufacturer Model Notes
Mitsumi FX001DE 1
NEC CDR-250
CDR-260 2
NEC 2vi
Sony 55E 1
55D 1
Panasonic 571
Wearnes
    Notes:

    1. The Mitsumi and Sony cdroms may have problems because they are not 
       ATAPI 1.2 compliant. This should be fixed with updated drivers.

    2. NEC 260 cdroms that ship with some Gateway systems adhere to the 
       1.7 spec instead of 1.2. For these cdroms, the BASEDEV=IBM1S506. A 
       line in the OS2 config.sys file has to be edited as follows:

                BASEDEV=IBM1S506.ADD /A:x /U:y /ATAPI

       The /A switch refers to the adapter number that the cdrom 
       is attached to. The /U option references the unit or device 
       number on a particular adapter. The /ATAPI parameter 
       enables ATA Packet Interface protocol for the NEC 260. If the 
       cdrom is attached to the second IDE port or adapter in a 
       system and is the only device on the adapter you would 
       enter:
                BASEDEV=IBM1S506.ADD /A:1 /U:0 /ATAPI

941212 COULD NOT LOCATE VROBJ.DLL (OS/2 WARP BONUSPAK)

DESCRIPTION OF SYMPTOMS:

Customer is attempting to run the BonusPak Installation Utility (INSTALL.CMD). The program starts up and issues five "1 file(s) copied" messages and then pops up an error box that states: " BPIU.EXE - COULD NOT LOCATE VROBJ.DLL ".

SUMMARY OF RESOLUTION:

Somehow the customer's LIBPATH statement has been changed such that the ".;" (dot semicolon) has been deleted from the LIBPATH. The LIBPATH statement in CONFIG.SYS should look similar to this: LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS; continuing on to the end. NOTE: C is drive where OS/2 Warp is installed.

DETAILS OF RESOLUTION:

If your customer is experiencing this error with the BonusPak Installation Utility, have the customer check his CONFIG.SYS file and look for the .; in the LIBPATH statement. It normally should be the first entry in the list of subdirectories. On a newly installed machine it is the first item. It may however be located anywhere on the LIBPATH= line. Ask the customer if he might have edited this line in his CONFIG.SYS or installed any applications that stated that they were going to edit or update CONFIG.SYS. That will be the way to determine how the line might have gotten modified. OS/2 Warp needs the .; in the LIBPATH to function correctly.

A missing .; in the LIBPATH can result in all sorts of errors occurring with different programs of the BonusPak and the system in general.

941213 FLOPPY DOES NOT WORK IN WARP ON NCR 3333 SYS0049 ERROR

DESCRIPTION OF SYMPTOMS
   Floppy drive does not work in WARP.
   SYS0049 Error When accessing the A (Floppy) Drive
   Problems with the Floppy drive on the NCR 3333 DX2/66
SUMMARY OF RESOLUTION
   Have A T & T / NCR replace the system board.
DETAILS OF RESOLUTION
   Replace the system board. NCR acknowledges that this is a hardware   e
   problem with the system board (bad IC pack on the system board). This proble
   occurs on many multi-tasking operating systems including OS/2, NT,  d Unix.
   and Unix. Call A T & T at 800 262-7782 (as of Dec 1994) and ask them  the
   to replace the system board due to FLEX DRIVE problems. This is AT&T / NCR Defect Number 86647.

941214 COREL DRAW! 3.0 WON'T START UNDER OS/2; GETS ERROR COREL DRAW 3 SECTION DRAWDIR=KEY NOT FOUND IN WIN.INI

DESCRIPTION OF SYMPTOMS: When trying to run Corel Draw! 3.0 for Windows under OS/2 the user cannot run the application and gets error, "Corel Draw 3 section drawdir=key not found in WIN.INI." Corel Draw! cannot be run.

SUMMARY OF RESOLUTION: 1. Modify WIN.INI file to address missing entry.

2. It may be possible to simply modify the PATH statement in the OS/2 AUTOEXEC.BAT file to include the Corel Draw directory so that the CORELDRW.INI file can be found.

DETAILS OF RESOLUTION:

   1.  Edit the WIN.INI file and add the following:
           {CorelDraw3.
           drawdir=C:\CorelDrw
       NOTE: CorelDraw3 is enclosed in square brackets.
             Also the directory may be modified as needed.
   2.  The user may also be able to modify the AUTOEXEC.BAT file of
       OS/2 so that the PATH statement includes whatever directory
       Corel Draw! 3.0 is located in, such as C:\CorelDrw as
       above

941216 OS/2 WARP ENHANCED IDE SUPPORT

                                                   SYSTEMS WITH
                             NATIVE SUPPORT      TRANSLATED BIOS*

ENHANCED IDE FEATURE

                               DOS    OS/2           DOS    OS/2

DRIVES > 1024 CYL (> 528 MB)

BOOT PARTITIONS < 1024 CYL    YES    YES            YES    YES
ACCESS DISK PAST 1024 CYL      NO     NO            YES    YES
LOGICAL BLOCK ADDRESSING       NO    YES             NO    YES
                             with parameters     with parameters
for performance               /A:0 /U:0 /LBA      /A:0 /U:0 /LBA
saves drive 3 multiplies
FASTER PIO MODE               YES    YES            YES    YES
DMA ADDRESSING                 NO     NO             NO     NO
 not prevalent on controllers
 advantage for EISA systems only
WD UTILITY "ON TRACK"         YES     **             NA     NA
 provides BIOS translation for
 system without translated BIOS
  • IBM Systems with translated BIOS include Valuepoint and IBM
 Mobile
    • On Track will have a OS/2 filter that provides translation at
  Warp ship.  This filter will be shipped with On Track other
  Enhanced IDE Utilities with WD and IBM hard files for use on
  systems that do not have translated BIOS.  In the meantime
  we have worked with On Track to have FDISK identify the
  signature (45H) to prevent corruption.

941227 FAXWORKS AND US ROBOTICS SPORTSTER 14400 MODEM

DESCRIPTION OF SYMPTOMS:

Cannot receive fax
Cannot dial
Modem not responding

SUMMARY OF RESOLUTION: Additional command for modem strings will relieve problems encountered on US Robotics Sportster 14400 modem with fax programs, specifically Faxworks by Softnet.

DETAILS OF RESOLUTION: The following is a complete string given by Softnet, which will turn off request to send, and resolve problems with Faxworks, and US Robotics Sportster 14400 modem:

&H2&I2&R1S36=0

950110 USING ALT+F1 ROUTINE UNDER WARP ON A PRELOAD SYSTEM

DESCRIPTION OF SYMPTOMS

If a user has a preloaded system and excutes the ALT+F2 command, selecting the maintenance partition (M), some information in the \OS2\BOOT\CONFIG.M file may be incorrect for that particular preload system. If the information is incorrect, when the install program is started, it may exit with an error indicating that the sourcepath incorrect.

RESOLUTION

To get around this problem, the user will have to edit the \OS2\BOOT\CONFIG.M file. There are two "set" statements that will need to be changed:

SET SOURCEPATH=drive:\path
SET FDISKETTESOURCE= 0 or 1;
    0 if redirected from cd, remote or local drive
    1 if user will be prompted to insert diskettes

If the user has not made a set of diskettes using their Diskette Factory program, then SOURCHPATH needs to points to C:\DISKETTS\OS2V3, and FDISKETTESOURCE should equal 0. If the user has made a set of installation diskettes and the install directory tree loaced under \DISKETTS\OS2V3 has been deleted by the Diskette Factory program, then SOURCEPATH should equal A: and FDISKETTESOURCE should be set

950111 SYSTEM HANGS ON THE FIRST REBOOT WITH TRAP0003 CS : EIP = 0568 : 00002913 and CSLIM = 00002aa8 ( WARP )

DESCRIPTION OF SYMPTOMS
   TRAP0003 on the first reboot installing OS/2 WARP.
   ********************* TRAP 32-bit ***********************
     TRAP =0003 ERRCD=0000 ERACC=**** ERLIM=********
     EAX  =00000000 EBX  =007601a8 ECX  =fdf10358 EDX  =000005a8
     ESI  =00000358 EDI  =fc8005a8 EBP  =00004dcc FLG  =00003002
     CS:EIP=0568: 00002913 CSACC=009b CSLIM= 00002aa8
     SS:ESP=0030:00004dc6 SSACC=1097 SSLIM=00003fff
     DS   =0570 DSACC=0093 DSLIM=000002d2 CR0  =8001001b
     ES   =0030 ESACC=1097 ESLIM=00003fff CR2  =feda4000
     FS   =0000 FSACC=**** FSLIM=********
     GS   =0000 GSACC=**** GSLIM=********
     ERROR AT LOCATION # 0160:fff5c34c - 000d:a34c
         60000, 9084
         048600b4
      INTERNAL REVISION  8.162      94/09/19
      Failure Mode : Installing WARP first reboot.
    ***************** end TRAP 32-bit ****************
RESOLUTION

This is related to the ATAPI fix for IBM 2.x /3.x IDE CD driver for IDE CDROM drives (PDDB FFWFC). User has an IDE NEC 260 CDROM. Downloaded ATAPI.ZIP from our BBS. Please follow the README.TXT. (919 517 0001)

Bootup the Installation disk and F3 out on Disk #1 at the Easy/Advance screen. This will get to the CDROM prompt (ie F:\OS2IMAGE\DISK1 where F is the cdrom drive, assuming this is a cdrom installation).

Go to the drive where WARP is installed (ie C: ) and change to \OS2\BOOT subdirectory. Check the file IBM1S506.ADD. It should be dated 11/18/94 and size is 27312. If not, it is an older file.

 Check to see if IBM1S506.ADD is NOT Read Only (using DIR /AR).
 If the attribute shown Read only, user must use the ATTRIB command to
 take off the Read only attribute.
 ATTRIB.EXE has not been unpack during the first phase of install, user
 must unpack this file.  It is on Disk #12 and is packed (ATTRIB).
 Go to \OS2 subdirectory and execute the following command:
 UNPACK F:\OS2IMAGE\DISK12\ATTRIB
 This should unpack ATTRIB.EXE to \OS2 subdirectory.
 Go to \OS2\BOOT subdirectory and execute the following command to
 take the Read only off the IBM1S506.ADD:
    ATTRIB -R IBM1S506.ADD
 Copy the new IBM1S506.ADD to this \OS2\BOOT subdirectory.
 Take out the disk on drive A: and reboot and continue with the second
 phase of the installation.

950111 WIN32S SUPPORT LIMITATIONS UNDER OS/2 3.0 WARP

DESCRIPTION OF SYMPTOMS

Versions of WIN32S above 1.1 are not supported under OS/2 V3.0

SUMMARY OF RESOLUTION

Check the version of WIN32S

DETAILS OF RESOLUTION

Any application which utilizes the 32 Bit API library "WIN32S" installs the version necessary for the application to run. A WIN32S.INI file is placed in the WINDOWS\SYSTEM directory and in it, the version of WIN32S is revealed. The README found in the root directory documents support for WIN32S being at versions 1.0 and 1.1. If the installed version is greater than 1.1, it is not supported.

950111 ATAPI.ZIP CONTAIN IBM OS/2 2.X / 3.X IDE CD DRIVER FOR IDE CDROM DRIVES

You MUST use these NEW files to replace the existing copies supplied by whatever version of OS/2 you are using.

Installation if OS/2 is already installed on your fixed disk

1. you must run Selective Install to install the files for the OS/2
   CD-ROM Device Manager and OS/2 CD-ROM File System.
 a. Open the OS/2 System folder on the desktop.
 b. Open the System Setup folder.
 c. Open Selective Install
 d. Select the CD-ROM Device Support check box
 e. Select OK
 f. Scroll to the bottom of the CD-ROM device list table and
    select the choice OTHER (OS/2 2.1) or Non-listed IDE CD-ROM (WARP)
 g. Select OK
 h. Select the OK push button to proceed from the System
    Configuration screen to the OS/2 Setup and Installation window
 i. Select Install
 j. When prompted to do so, insert the numbered installation
2. Copy the files provided in this package OVER those installed in
   step 1, to their proper location on your system.  On Warp this is
   \OS2\BOOT. Check by doing a 'DIR IBM1S506.ADD /S' on your system
   <== DIR command
3. IDE CD ROMs that adhere to the ATAPI specification of February 1994
   will be detected automatically if they are configured on the
   Primary or Secondary IDE channel.  If your IDE channel is not
   the primary or secondary,
   or if your IDE channel is not using the default io ports and IRQs,
   do a 'HELP IBM1S506.ADD' at an OS/2 command prompt to get detailed
   information on changing or adding channels.
4. Some drives do not respond to an ATAPI command from the February
   Spec.These drives can not be auto detected and require an additional
   parameter on the IBM1S506.ADD line in config.sys. The NEC 260 drive,
   for example, requires this additional parameter.
   BASEDEV=IBM1S506.ADD /A:x /U:y /ATAPI
   where x is the adapter number and y is the unit number.
   /A:
    Which IDE drive connector on your adapter contains the cable
    that the NEC 260 IDE drive is connected to
    IF you have only one IDE controller, this is Adapter 0, /A:0
    IF you have TWO IDE controllers, and the IDE CDROM is connected
    the second controller cable, this is Adapter 1, /A:1
    The Enhanced IDE specifications allow for FOUR adapters, so
    /A: COULD also be 2 or 3 in your system.
   /U:
 Each IDE controller can drive up to TWO drives. If the CD drive
 is jumpered as the Master then this is unit 0, /U:0 otherwise it
 is unit 1, /U:1  It is not possible to have a device configuredas
 Slave without a Master on the same controller.
 /atapi or /ATAPI
 This informs the IBM1S506.ADD driver that this unit (/a: /u:) is an
 ATAPI (IDE attached) CDROM drive...
 Editing your config.sys...
 locate the BASEDEV=IBM1S506.ADD line
 If you have NO parameters on this line, then ADD the
 parms as defined above, /A:? and /U:?
 an example line with the CD as slave on controller 1
 BASEDEV=IBM1S506.add /A:0 /U:1 /ATAPI
 IF you ALREADY have parms, and have a /A:? parm already, make sure
 to add JUST the /U:? parm for that adapter.
5. IF you are using OS/2 2.11 or earlier, you will need to add the
 following config.sys statement.(If you have WARP, choosing 'NON listed
 IDE CDROM will cause this line to be placed in config.sys
 automatically)
 BASEDEV=IBMIDECD.FLT
6. Shut down and restart your system
Installation if OS/2 is NOT already installed on your fixed disk
----------------------------------------------------------------
1. create the CD install disk 1 from the OS/2 CDROM
2. copy the files supplied here OVER the ones on disk 1.
3. If you have a NEC 260 IDE CDROM drive, edit the config.sys on disk 1
   and modify the BASEDEV=IBM1S506.ADD line as described above
   (adding the /A & /U parms)
3a. If you are using OS/2 2.11 or earlier, add the following statement
   to config.sys and copy the associated file onto disk 1.
    BASEDEV=IBMIDECD.FLT
3b. If you are using OS/2 WARP, add the following statement to the
    config.sys on the DISKETTE 1:
    SET COPYFROMFLOPPY=1
4. Boot the installation disk and disk 1 and proceed thru
   installation phase 1.
5. (If you are using OS/2 WARP, skip to step 7)
   Because the installation program uses copies of these files
   from a packed file on the installation diskettes, the
   UPDATED drivers you copied in step 2 are overlayed with the
   older ones on your hard disk.  You MUST manually fix this.

When you are asked to reboot to continue the installation,

   insert the installation disk and press Ctrl-Alt-Del, then through
   disk 1 to the install panel. Press F3 to get to a command line.
   Go to the installation drive (wherever you installed OS/2).
   You will need to clear the read-only attribute on the IBM1S506.ADD
   file.  Do this by typing:          (OS/2 2.1 & 2.11)
              /os2/attrib -r \os2\ibm1s506.add
   Copy the updated files (OS2CDROM.DMD, IBM1S506.ADD, and
   IBMIDECD.FLT from disk 1 to the proper location on the install
   partition)
6. type EXIT from the command line
7. remove the diskette from A: and reboot
8. Complete the rest of install
******************
   NOTE:  This is a README.TXT file from this ATAPI.ZIP package
   available on the IBM BBS 919 517 0001.  Is is on LIB #17 OS/2
   Device Drivers. Also under the SAME name on CIS and other BBS's.
   ATAPI.ZIP      45862    12-29-94   OS/2 2.x/3.x IDE

950116 INSTALLATION OF WARP, IT DOES NOT RECOGNIZE CDROM SONY 541 WHICH IS CONNECTED TO A FUTURE DOMAIN 1600 SERIES SCSI CARD

DESCRIPTION OF SYMPTOMS

WARP does not recognize the Sony CD-ROM which is connected to the Future Domain 1600 ( FD16-700.ADD ).

RESOLUTION

This SONY 541 is SCSI II type CD-ROM. It is compatible and work with the FD16-700.add device driver. Users need to make sure the SCSI ID for the SONY is NOT 0 or 1. In this case, user has changed the ID to 2 and WARP is abled to recognize the SONY CD-ROM.

950116 OS/2 WARP NOT RECOGNIZING SONY 31A CDROM WHICH IS ATTACHED TO A CARDINAL DSP16 (SOUNDBLASTER COMPATIBLE)

DESCRIPTION OF SYMPTOMS

OS/2 WARP does not recognize the SONY 31A which is connected to the Cardinal DSP16 card. Installation asks for the CD but keeps looping and ask for the CD again and again.

SUMMARY OF RESOLUTION

User is using downloaded driver (SONY31A.ADD) and followed the parameter from page 329 example 4 of the user's guide. As default, the sound port address is 220h and IRQ 5. The CDROM is set for port address 300 and IRQ 12.

User should use the driver that came with OS/2 WARP and added the following to the SONY31A.ADD statement: SONY31A.ADD /A:0 /AT:05 /P:0300 /I:12 /V where the port address and irq above should be for the cdrom, NOT the soundcard. The /P: is the address of the cdrom and the /I: is the IRQ of the CDROM drive. (the /v only showed us if the cdrom was recognized when the driver loaded or not).

Note: the above problem is happen if user put the wrong port address and irq for the cdrom.

950116 INSTALLING WARP AFTER THE FIRST PHASE, GET ERROR MESSAGE " OS2KRNL IS NOT ACCEPTABLE ... "

DESCRIPTION OF SYMPTOMS

OS2KRNL is unacceptable on the first reboot when installing WARP on system with a Micropolis 2112mb SCSI drive. It is connected to a Future Domain card.

RESOLUTION

Users need to contact Micropolis for assistance getting an upgrade ROM for this 2gb drive to work under OS/2 WARP

950116 USING STACKER V1.1 FOR OS/2 UNDER WARP

DESCRIPTION OF SYMPTOMS

Systems extended logical partitions are not being recognized by WARP This is because the drives are stacked, using Stacker software.

RESOLUTION

Called Stacker to get the lastest info on their version 1.1 for OS/2. Stacker stated that in order for Stacker for OS/2 1.1 to work proper with WARP users need to download and install a fix ( SWARP.EXE ) from their BBS (619) 431-5956. Their technical support number is (619) 929-3900.

950117 INSTALLING OS/2 WARP ON A SYSTEM WITH NCR PCI SCSI CONTROLLER THAT USED OS2CAM.ADD, RECEIVED C:\OS2\SYSTEM\COUNTRY.SYS ERROR AFTER INSTALLATION

DESCRIPTION OF SYMPTOMS
Error after successful installation of WARP:
" C:\OS2\SYSTEM\COUNTRY.SYS CANNOT BE FOUND "
RESOLUTION
User's system is as followed:
A clone 486dx2-66mhz, 16mb, AWARD bios version 4.5, PCI system,
and a built-in NCR PCI SCSI on the system board.
It came with an OS/2 driver called OS2CAM.ADD.
User has added in the config.sys on Disk #1 and was abled to install
OS/2 thru all the disks, but after reboot, before the desktop, it will
display the above error msg.
Check the config.sys and the OS2CAM.ADD is in there but the following
statement is not in there:
   BASEDEV=OS2SCSI.DMD.
Do the following:
Moves the BASEDEV=OS2CAM.ADD after BASEDEV=OS2DASD.DMD.
Adds the BASEDEV=OS2SCSI.DMD below the OS2CAM.ADD and reboot.
System will boots up and running OS/2 WARP.
Please note that this driver is supported only from NCR vendor. It does
not come with the OS/2 WARP package.

950118 INSTALLED WARP AND LOST ACCESS TO (ATM) ADOBE TYPE MANAGER 3.0 FOR WINDOWS

DESCRIPTION OF SYMPTOMS
   Installing WARP on a sysem with Adobe Type Manager 3.0 will
   'backlevel' to ATM ver. 2.5. You will also loose access to any
   imported fonts already on the system.
SUMMARY OF RESOLUTION
   Depending on how WARP  is installed (bootmanager or dualboot)
       will determine how to modify the system.
       1. Dualboot
          Installation of WARP will replace the current ATM.INI in the
          WINDOWS subdirectory.
       2. Bootmanager
          Installation of WARP may point to the x:\psfonts subdirectory
          partition where it is installed and not to the path in the or
          in the ATM.INI file.
        .Setup.
        PFM_Dir=c:\psfonts\pfm
        PFB_Dir=c:\psfonts
        .Settings.
        ATM=On
        QLCDir=c:\psfonts
        Version=3.0
        TmpDir=c:\
DETAILS OF RESOLUTION
   1. Dualboot
          a. Prior to installation of WARP
          Rename the current x:\windows\psfonts directory to
          x:\windows\tpsfonts.
          Rename or backup the current ATM.INI file.
          Reinstall Adobe Type Manager 2.5, 2.6, or 3.
          After installation, copy the contents of x:\windows\tpsfonts
          x:\windows\tpsfonts\pfm to the x:\windows\psfonts and
          x:\windows\psfonts\pfm directories
          b. After installation of WARP
          Rename the current x:\windows\psfonts directory to
          x:\windows\tpsfonts.
          Reinstall Adobe Type Manager 2.5, 2.6, or 3.0
          After installation, you can add the fonts from the the ATM co
          panel ADD feature choosing x:\windows\tpsfonts\pfm in the
          directories window.
       2. Bootmanager
          If Windows is on the same partition that WARP will be install
          follow proceedure 1a above. If WARP is installed on a differe
          partition, edit the ATM.INI file to mirror the appropriate li
          in .SETUP. and  .SETTINGS. example above, and reinstall ATM
          from disks.

Note: Applications that are migrated will need the WIN_ATM in t notebook set to on. It may also be necessary to reinstall specia fonts not included with ATM.

950117 UNDOCUMENTED PARAMETER ON THE BOOT COMMAND: BOOT /DOS /N

DESCRIPTION
BOOT /DOS /N
The /N will do the preparation with the disk, but it does not reboot.
User can then do a shutdown as normal.
It will shows the following:
SYS1716: Warning! You should now restart your system by
selecting Shutdown from the desktop, or pressing Ctrl+Alt+Del.
EXPLANATION: The program made changes to your hard disk and
replaced files C:\CONFIG.SYS and C:\AUTOEXEC.BAT in
preparation for the next reset.
ACTION: Restart your system by selecting Shutdown from the
desktop, or pressing Ctrl+Alt+Del.

950118 TIMING HANG ON IBM PC 300 SERIES - 486 SYSTEMS AND ON ALL APTIVA'S FROM THE 310 (2144-22P) THROUGH THE 530 (2144-66P)

DESCRIPTION OF SYMPTOMS
When the IBM PC 300 Series - 486 Systems  BIOS code switched CMOS
banks, OS/2 (and the physical clock Device Driver) did not know
that the CMOS bank was switched. If an IRQ 8 (realtime clock
interrupt) came in when the CMOS bank was switched, then the system
would hang because the clock DD would read the RTC CMOS locations
on the 2nd bank when it should have read them on the 1st bank.
The OS/2 virtual DD (VCMOS.SYS) did not allow writes to CMOS with
addresses < 0Eh.  So, the Rapid Resume data could not be written by
a VDM (DOS session or windows).  VCMOS.SYS virtualizes ports 70H
and 71H.
RESOLUTION

VCMOS.SYS will now virtualize ports 22H and 24H when on IBM PC 300 Series - 486 Systems or Aptiva. A fix must be applied to the OS/2 system to correct this problem.

How to apply the fix

In the fixes sent to you will be a file called VCMOS.SYS. After the install is complete, copy VCMOS.SYS to ?:\OS2\MDOS directory (? is the drive you installed OS/2 into).

950118 INSTALLING WARP ON AN APTIVA, AN IBM PC 300 AND 700 SERIES MACHINES WITH 3.7MB OF MEMORY AND AN IDE CDROM RESULTS IN TRAP0003

DESCRIPTION:

Trap 3 can happen on IBM PC 300 Series - 486 Systems , IBM PC 300 Series - Pentium System , IBM PC 700 Series - Pentium Systems and Aptiva machines with 3.7 meg of memory and an IDE CDROM

The queueing mechanism in the IDE CDROM driver can cause a trap 3 during install if there is heavy swap activity. A fix must be applied to the OS/2 system to correct this problem.

How to apply the fix for a CD install.

OS/2 has two diskettes that are required to boot and initiate an install from a CD. The diskettes are called the "Installation" diskette and "Diskette 1". In the fixes sent to you will be a file called IBMIDECD.FLT. Copy this file to "Diskette 1" replacing the original that was on the diskette. Now go forth and do your install as usual. The new module will be used during the install and it will be installed on the final system.

How to apply the fix for a diskette install.

Boot the Install diskette and go through the first part of install. At the end of the first part of install, a blue screen with white letters comes up telling the user to remove the diskette and press enter to reboot and continue the install. At this time, the user must press the F3 button to get to a command line. In the fixes sent to you will be a file called IBMIDECD.FLT. Copy this file to the directory ?:\OS2\BOOT (? is the drive letter being installed into) replacing the original. Then enter EXIT to get you back to the blue screen. Now go forth and finish your install as usual. the new module will be used during the install and it will be installed on the final system.

The fix is AVAILABLE in the APTIVA UPDATE. A replacement disk will be sent. For the CD-ROM version of WARP, a new Diskette #1 will be sent. For the Diskette version, a new Diskette #2 will be sent. Use this new diskette in place of the equivalent diskette that came with OS/2 WARP.

950118 APTIVA MACHINES WITH THE ARIA SOUND CARD. (WARP)

DESCRIPTION OF SYMPTOMS
   The APTIVA machines 530 (2144-66P) & 730 (2144-86P).
   The ARIA soundcard needs the promethieus driver for OS/2 and
   it will not be available till 1995.  The main symptoms
   that the user will see is:
   1. No sound under OS/2.
   2. Windows seamless applications open but disappear and are
      not in the task list.
DETAILS OF RESOLUTION
   If the machines equipped with this soundcard (ARIA), the
   sound MUST be disabled.  User must do the following:
   1. Go into fullscreen Windows Program Manager
   2. Open the "Control Panel" folder
   3. Start the "Drivers" program
   4. Remove the two ARIA drivers
   5. Exit Windows

The applications should run seamlessly now

950118 APTIVA APPLICATION PROBLEMS UNDER WARP

DESCRIPTION OF SYMPTOMS

After installing WARP on Aptiva machines there are a number of problems with the applications that are shipped with the machine. Below are some problems are being identified and fixes: 1. The proper icons for some of the applications is replaced by the

  OS/2 standard Windows icon.  This will be fixed in a future release
  of OS/2.

2. For Undersea Adventure and Discoverers do the following:

 a. Edit the file C:\SEA\KA.CNF and change the CDdrive field from E
    to D and do a change of all the E: to D:.  Save the changed file
 b. Edit the file C:\SEA\SEA.BAT and change of all the E: to D:.
    Save the changed file
 c. Edit the file C:\SEA\DISCOVER.BAT and change of all the E: to
    D:.  Save the changed file
 d. Go to the "Settings" notebook for each of the two programs by
    doing the following and make the indicated changes:
    1) Point the mouse pointer at the icon
    2) Press the right mouse button once to get the context menu
    3) Move the mouse pointer to Settings and press the left mouse
       button once
    4) Change the "Path and file name:" field from
       C:\SEA\PS1CDROM.EXE (in the Undersea Adventure)
       C:\DISCOVER\PS1CDROM.EXE (in the Discoverers) to
       C:\WINDOWS\PS1CDROM.EXE
    5) Press the left mouse button on the "Session" tab
    6) Press the "WIN-OS/2 settings button
    7) Select the DOS Memory settings
    8) Set DOS_HIGH to ON
    9) Set DOS_UMB to ON and save the settings
   10) Select the button for WIN-OS2 full screen
   11) Double click the control box in the upper left corner of the
       "Settings" notebook to close it.
   Note: Sound currently does not work for the Discoverers
         application.  This is being worked on.

3. Reuters - When Reuters (Money Network) is started from it's

  migrated icon or from Windows Program Manager it displays "...not
  enough file handles..." dialog. Program can not open or create
  files. The README.WRI file recommends 100 file handles be specifies
  when running under OS/2.  Set DOS_FILES to 100 with the following
  steps:
a. Point the mouse pointer at the Reuters icon
b. Press the right mouse button once to get the context menu
c. Move the mouse pointer to Settings and press the left mouse
   button once
d. Press the left mouse button on the "Session" tab
e. Press the "WIN-OS/2 settings button
f. Select the Other DOS settings
g. Set DOS_FILES to 100 and save the settings
h. Double click the control box in the upper left corner of the
   "Settings" notebook to close it.

4. The following are some of the problems being addressed.

a. Music Mentor gets a General Protection Fault when the "To
   Session" button is pressed.
b. Rapid Resume does not currently work under OS/2
c. Running Disney Software Preview seamless hangs the system

950119 CDROM in ThinkPad DockII (using AHA152X) is not recognized.

DESCRIPTION OF SYMPTOMS

On IBM Thinkpad connected to Docking station II with cdrom connected to Adapted 1510,1520,1522 controller is not recognized after installation Trying to do selective install for cdrom system configuration shows no cdrom support which it did during initial installation, when he chooses cdrom as source directory program comes back with message invalid source directory.

SUMMARY OF RESOLUTION

PCMCIA drivers takes IRQ 11 on machine and IRQ 11 is default of the Adaptec SCSI adapter (in the docking station) and this IRQ conflict makes cd-rom unusable.

DETAILS OF RESOLUTION

Reconfigure SCSI card to IRQ 9 or to any other free IRQ through Dock II setup on bootup (Control A). Also Thinkpad has an IDE and on the docking station has a SCSI harddisk, than move the SCSI driver statements before IDE driver statements in config.sys.

OSWAFAIL - WIN-OS2 SESSION FAILS TO START

Item FFBJZ

01/30/95

SYMPTOM

When starting any WIN-OS/2 session, the session ends before it starts. If started from an ICON, it hatches then unhatches. If started from a command line, the "Loading Please Wait..." message appears, then the command prompt reappears.

If starting a WIN-OS/2 session from a command line with a "/B" switch, the BOOTLOG.TXT file shows LOADSTART=MOUSE.DRV as the last statement in the file.

RESOLUTION

Check the MOUSE.INI file and ensure the MOUSETYPE= statement is the same as the mouse installed on the system. The statement should read:

 MOUSETYPE=PS2        for a PS/2 mouse
 MOUSETYPE=SERIALx    Where x is the port being used by the mouse

When running in DOS/WINDOWS, the system queries the hardware attached and updates MOUSE.INI. This does not happen in OS/2. An APAR has been opened for the problem.