TITLE: 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.
TITLE: 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.
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:
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
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.
TITLE: 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.
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
.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"
TITLE: 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.
TITLE: 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 syste
TITLE: 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
TITLE: 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.
TITLE: 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.
TITLE: 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.
TITLE: 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.
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
----------------------------------------------------------------------
+--------------------------------------------------------------------+
| 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
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 hard-
ware 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.