home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
OS2
/
DOC211.ZIP
/
OS211DOC.TXT
< prev
Wrap
Text File
|
1994-02-04
|
137KB
|
3,857 lines
Updates to: Installation Guide and Using the
Operating System
Document Number 82G6228-00
February 4, 1994
+--- Note -----------------------------------------------------------+
| |
| Before using this information and the product it supports, be sure |
| to read the general information under Appendix A, "Notices" on |
| page 9. |
| |
+--------------------------------------------------------------------+
Contents
------------------------------------------------------------------------------
Part 1: Changes to OS/2 2.1 Installation Guide . . . . . . . . . . . . . ii
About This Book . . . . . . . . . . . . . . . ii
Before You Begin . . . . . . . . . . . . . . ii
Chapter 1. Choosing an Installation Procedure ii
Chapter 2. Installing OS/2 2.1 as the Only
Operating System (Basic Installation) . . . ii
Chapter 3. Adding OS/2 2.1 to a DOS System
(Dual Boot) . . . . . . . . . . . . . . . . ii
Chapter 4. Installing Multiple Operating
Systems (Boot Manager) . . . . . . . . . . . ii
Chapter 5. Using a Response File to Install ii
Appendix A. Adding Features and Changing Your
System Configuration . . . . . . . . . . . . ii
Appendix B. Diagnosing System Problems . . . ii
Appendix F. Migrating from OS/2 Extended
Edition to OS/2 2.1 . . . . . . . . . . . . ii
Appendix G. Upgrading the BIOS of Your
Computer . . . . . . . . . . . . . . . . . . ii
Appendix H. Notices . . . . . . . . . . . . ii
------------------------------------------------------------------------------
Part 2: Changes to OS/2 2.1 Using the Operating System . . . . . . . . . ii
About This Book . . . . . . . . . . . . . . . ii
New Features in OS/2 2.1 . . . . . . . . . . ii
Chapter 1. Getting Started with OS/2 2.1 . . ii
Chapter 4. System Setup . . . . . . . . . . 1
Power . . . . . . . . . . . . . . . . . . . 1
PCMCIA . . . . . . . . . . . . . . . . . . 5
Chapter 5. Startup . . . . . . . . . . . . . 5
Chapter 6. Drives . . . . . . . . . . . . . 5
Chapter 8. Productivity . . . . . . . . . . 6
Chapter 10. Information . . . . . . . . . . 6
Chapter 12. Drive A . . . . . . . . . . . . 6
Chapter 16. Printers and Plotters . . . . . 6
Chapter 17. Preparing Your Programs . . . . 6
Chapter 18. Using Windows Programs . . . . . 6
Chapter 23. Audio Support for Applications . 6
Part 5: Extra Help . . . . . . . . . . . . . 6
Chapter 24. Solving Problems . . . . . . . . 6
Chapter 26. Software Support . . . . . . . . 6
Chapter 27. Video Support . . . . . . . . . 6
Chapter 28. Printer Support . . . . . . . . 6
Chapter 29. Hardware Support . . . . . . . . 6
Appendix B. Error Messages . . . . . . . . . 8
Appendix C. Backing Up and Restoring Your
Desktop . . . . . . . . . . . . . . . . . . 8
Appendix F. Removing Programs . . . . . . . 8
Appendix A. Notices . . . . . . . . . . . . 9
Trademarks and Service Marks . . . . . . . . 9
About This Booklet
The purpose of this booklet is to provide you with
updates to the OS/2 2.1 Installation Guide and the
OS/2 2.1 Using the Operating System book.
Keep this booklet as a reference and look here
first before referring to the Guide or Using book.
HOW TO USE THIS BOOKLET
_______________________
This booklet should be used in conjunction with
the Installation Guide and Using the Operating
System book. Only chapters that have changes are
listed in this booklet. All changes begin with a
reference to the page in the original
documentation on which the change is to be made.
Note: Because some of these changes are lengthy,
you might want to make a notation on the
original page referring to the update
located in this booklet.
HOW THIS BOOKLET IS ORGANIZED
_____________________________
This booklet is organized into the following
parts:
o Part 1 contains changes to the OS/2 2.1
Installation Guide.
o Part 2 contains changes to the OS/2 2.1 Using
the Operating System.
CONVENTIONS USED IN THIS BOOKLET
________________________________
The following conventions are used in this booklet
to help distinguish elements of the text:
+---------------+--------------------------------+
| Text Element | Use |
+---------------+--------------------------------+
| bold | Indicates the name of an item |
| | you that you can select. |
+---------------+--------------------------------+
| italics | Indicates the first time a new |
| | term is used. A definition of |
| | the term immediately follows |
| | the italicized terms. Italics |
| | are also used to indicate a |
| | book title or variable |
| | information that must be |
| | replaced by an actual value. |
+---------------+--------------------------------+
| monospace | Indicates an example such as a |
| | fictitious path and file name |
| | or text that is displayed on |
| | your screen, such as an error. |
+---------------+--------------------------------+
| UPPERCASE | Indicates a file name, command |
| | name, or acronym. |
+---------------+--------------------------------+
| * | Indicates trademarks of the |
| | IBM Corporation. |
+---------------+--------------------------------+
| ** | Indicates trademarks of other |
| | companies. |
+---------------+--------------------------------+
PART 1: CHANGES TO OS/2 2.1 INSTALLATION GUIDE
Part 1 contains information that is new or
different from the information in the OS/2 2.1
Installation Guide.
The chapter numbers and titles in this booklet are
the same as those used in the Installation Guide;
only those chapters of the Guide that are changed
are included here.
ABOUT THIS BOOK
_______________
> On page x, add the following entry to the list
in the section titled "How This Book Is
Organized":
o Appendix H provides information on
creating a startup diskette for OS/2(*)
2.1.
Note: The original Appendix H, "Notices" is
now Appendix I, "Notices".
BEFORE YOU BEGIN
________________
> On page xiii, replace the second paragraph
with the following:
Late-breaking information about installation
can be found in the README.INS file. This
file is located on Diskette 3 of the diskette
package and on Diskette 1 of the CD package.
> On page xiii, add the following minimum
requirement:
o At least CGA video support.
> Under the section titled "Questions About Your
Current Computer System" on page xiv, add the
following questions and answers:
o Are you installing on an EISA system with
an Adaptec(**) 1742A controller card?
If you have an EISA system with an Adaptec
1742A controller card and you want to
install OS/2 2.1, you must run the Setup
Configuration program provided on the
Adaptec Card Setup Diskette. To set up
the Adaptec card in the configuration
using the Setup Diskette, do the
following:
1. Set the Enhanced mode setting to OFF.
2. Set the Standard mode setting to ON.
3. Set the Hex Address setting to C800.
4. Set the I/O Port setting to 230H.
5. Set the DMA channel setting to 5.
6. Set the Parity Check setting to OFF.
7. Set the Synchronous Negotiation
setting to ON. If CD-ROM is not
recognized, set this setting to OFF.
8. Set the Enabled Disconnect setting to
YES.
9. Set the IRQ setting to 11 (default is
2).
o Are you installing OS/2 2.1 on an IBM(*)
ThinkPad(*) with a Docking Station(**)?
If you are installing OS/2 2.1 on an IBM
ThinkPad 700, 700C, 720, or 720C attached
to a 3550 Docking Station, you need to
replace the ABIOS files on the OS/2
Installation Diskette with files from the
Reference Diskette. Do the following:
1. Detach the ThinkPad from the Docking
Station.
2. Create a Reference Diskette by
following the documentation that came
with the ThinkPad.
3. Make a copy of the Installation
Diskette.
4. Remove the copy and insert the
original Installation Diskette into
drive A.
5. Turn on the computer. If it is
already on, press and hold Ctrl+Alt
and press Del to restart the system.
6. When you are prompted to do so, remove
the Installation Diskette, insert
Diskette 1, and press Enter.
7. When the Welcome screen is displayed,
press Esc to display the command
prompt.
8. Insert the copy of the Installation
Diskette into drive A.
9. Type:
A:\DEL *.BIO
and press Enter.
10. Remove the copy of the Installation
Diskette, and insert the Reference
Diskette you created in step 2 into
drive A.
11. If your computer has more than one
diskette drive, insert the copy of the
Installation Diskette into drive B.
In the next two steps, you will be
prompted to insert diskettes into both
drive A and drive B.
If your computer has only one diskette
drive, when you are asked to insert a
diskette into drive A, insert the
Reference Diskette into your diskette
drive. When you are asked to insert a
diskette into drive B, insert the copy
of the Installation Diskette into your
diskette drive.
12. Type:
COPY A:\*.BIO B:\
and press Enter.
13. Type:
COPY A:\ABIOS.SYS B:\
and press Enter.
14. Turn off the ThinkPad and return it to
the Docking Station.
15. Restart the installation procedure by
inserting the copy of the Installation
Diskette into drive A.
o Are you installing on a system with an AOX
upgrade?
If you have a system with a 286 processor
that has been upgraded to a 386SX with an
AOX upgrade and you want to install OS/2
2.1, you must start the system with DOS
and run the AOX232.EXE. To request the
AOX232.EXE, contact the AOX Technical
Support Group at 1-800-232-1269.
> On page xv, add the following note after the
question "Is your display adapter an ATI(**)
Graphics Ultra(**) Pro?":
Note: If you have a Gateway 2000(**) system,
refer to "Black Lines on an OS/2 Logo
Screen" for further instructions.
> On page xvii, add the following header before
the third paragraph:
SCSI-Based CD-ROM Support
> On page xvii, add the following section to the
end of the page:
Non-SCSI CD-ROM Support for Sony, Panasonic,
and Mitsumi
For the Sony(**), Panasonic(**), and
Mitsumi(**) non-SCSI drives to be recognized
by OS/2, the base port address specified on
the CD-ROM BASEDEV statement in CONFIG.SYS
must match the base I/O port address specified
on the CD-ROM host adapter card.
Note: If you are installing OS/2 2.1 from a
CD-ROM, you might first need to modify
the BASEDEV statement for your CD-ROM
device driver in the CONFIG.SYS file on
the diskette labeled Diskette 1.
Modifying CONFIG.SYS for the Sony CDU-31A
Device Driver:
The examples that follow illustrate how this
CD-ROM is attached to the most common host
adapters and indicate the required parameter
switch settings for each CD-ROM drive.
Example 1: The Sony CDU-31A CD-ROM drive is
attached to a Sony CDB-334 host adapter.
The Sony CDB-334 host adapter supports base
I/O port addresses of 320h, 330h, 340h, or
360h. If the host adapter is set to its
default port address of 340h, the CONFIG.SYS
statement does not need to be modified and
should appear as follows:
BASEDEV=SONY31A.ADD
If the CDB-334 host adapter is set to any port
address other than the default of 340h, the
CONFIG.SYS statement must be modified. For
example, if the Sony CDB-334 host adapter is
set to a base I/O port address of 360, the
line in the CONFIG.SYS file should appear as
follows:
BASEDEV=SONY31A.ADD /A:0 /P:0360
Example 2: The Sony CDU-31A CD-ROM drive is
attached to a Media Vision(**) ProAudio
Spectrum(**) 16 host adapter.
In this case, the line in CONFIG.SYS must be
modified and should appear as follows:
BASEDEV=SONY31A.ADD /A:0 /AT:08
Example 3: The Sony CDU-31A CD-ROM drive is
attached to a Creative Labs Sound Blaster(**)
Pro, Sound Blaster 16, or Sound Blaster 16
MultiCD host adapter.
The port address specified on the BASEDEV
statement in CONFIG.SYS should be 10h above
the base I/O port address specified on these
adapter cards. For example, if the Sound
Blaster card is set for a base I/O port
address of 220h, the line in CONFIG.SYS should
appear as follows:
BASEDEV=SONY31A.ADD /A:0 /P:0230
Modifying CONFIG.SYS for the Panasonic Device
Driver:
The Panasonic device driver (SBCD2.ADD)
supports the following CD-ROM drives:
- Panasonic CR-521,522,523,562,563
- Creative Labs OmniCD
- IBM ISA CD-ROM drive
The examples that follow illustrate how this
CD-ROM is attached to the most common host
adapters and indicate the required parameter
switch settings for each CD-ROM drive.
Example 1: A Panasonic, Creative Labs OmniCD
or IBM ISA CD-ROM drive is attached to a
standard Panasonic or IBM CD-ROM host adapter.
The standard Panasonic or IBM host adapter
supports base I/O port addresses of 300h,
310h, 320h or 330h. For example, if the
adapter is set to a base I/O port address of
300, the line in the CONFIG.SYS file should
appear as follows:
BASEDEV=SBCD2.ADD /P:300
Example 2: A Panasonic, Creative Labs OmniCD
or IBM ISA CD-ROM drive is attached to a
Creative Labs Sound Blaster Pro, Sound Blaster
16, or Sound Blaster 16 MultiCD.
If the Sound Blaster card is set for a base
I/O address of 220h, the line in CONFIG.SYS
should appear as follows:
BASEDEV=SBCD2.ADD /P:220
Example 3: A Creative Labs OmniCD is attached
to a standard Creative Labs CD-ROM host
adapter.
The standard Creative Labs host adapter
supports base I/O port addresses of 250h or
260h. For example, if the adapter is set to a
base I/O port address of 250, the line in the
CONFIG.SYS file should appear as follows:
BASEDEV=SBCD2.ADD /P:250 /T:2
Modifying CONFIG.SYS for the Mitsumi CD-ROM
Device Driver:
The examples that follow illustrate how this
CD-ROM is attached to the most common host
adapters and indicate the required parameter
switch settings for each CD-ROM drive.
Example 1: A Mitsumi CD-ROM drive is attached
to a Mitsumi host adapter.
The Mitsumi host adapter supports I/O port
address ranges from 300h to 3FCh. If the
Mitsumi host adapter is set to a base I/O port
address of either 300h or 340h, the statement
in CONFIG.SYS does not need to be modified and
should appear as follows:
BASEDEV=MITFX001.ADD
If the Mitsumi host adapter is set to an
address other than those specified above, the
BASEDEV statement needs to be modified. For
example, if the Mitsumi host adapter is set to
a base I/O port address of 320, the line in
the CONFIG.SYS file should appear as follows:
BASEDEV=MITFX001.ADD /P:320
Example 2: A Mitsumi CD-ROM drive is attached
to a Creative Labs Sound Blaster 16 MultiCD.
If the Mitsumi CD-ROM port on the Sound
Blaster 16 MultiCD is set to an I/O port
address of 320, the line in CONFIG.SYS should
appear as follows:
BASEDEV=MITFX001.ADD /P:320
> On page xviii, add the following note before
the second paragraph:
Note: Use the LOADDSKF utility program to
create diskette images, which are
compressed, binary images of a
diskette. The LOADDSKF.EXE is in the
\DISKIMGS directory of the CD.
LOADDSKF can be run from either the DOS
or OS/2 operating system.
> On page xix, add the following additional note
to the section titled "Additional Notes for
Users of OS/2":
o To avoid desktop problems such as a blank
desktop or duplicated icons, you need to
run CHKDSK /F and have at least 20MB of
free space in your OS/2 partition.
CHAPTER 1. CHOOSING AN INSTALLATION PROCEDURE
______________________________________________
> On page 6, replace paragraph 3 with the
following:
The amount of space you need for the OS/2 2.1
partition depends upon which features of the
operating system you are going to install.
The amount of space required is also related
to how much system memory your computer has
and how many applications will be running at
the same time.
If you are going to install all features of
the operating system, you need approximately
40MB of free disk space and a minimum of 10MB
of space for the SWAPPER.DAT file.
If you are going to install selected features,
you need from 20MB to 40MB. These
installation choices are described in more
detail in Chapter 2, "Installing OS/2 2.1 as
the Only Operating System (Basic
Installation)".
If you are going to install multimedia
support, you need up to an additional 5MB of
hard disk space.
CHAPTER 2. INSTALLING OS/2 2.1 AS THE ONLY
___________________________________________
OPERATING SYSTEM (BASIC INSTALLATION)
_____________________________________
> On page 16, replace the first 3 paragraphs
with the following:
Install preselected features If you select
this predetermined
set of OS/2
features, you will
need approximately
32MB of total disk
space for the
operating system
and its features
and a minimum of
10MB for the
swapper file.
Install all features If you select all
features, you will
need approximately
40MB of total disk
space for the
operating system
and its features
and a minimum of
10MB for the
swapper file.
Select features and install If you decide to
select the
features you want
to install, you
need from 20MB to
40MB of total disk
space for the
operating system
and its features
and a minimum of
10MB for the
swapper file.
> On page 24, add the following paragraph before
the sentence "To make a selection different
from the one listed in this window...":
For non-SCSI CD-ROM drives, if you cannot
access your CD-ROM device after installation,
ensure that the port address in the BASEDEV
statement in the CONFIG.SYS file on your
startup partition (hard drive) matches the
port address on the CD-ROM host adapter card.
See "Non-SCSI CD-ROM Support for Sony,
Panasonic, and Mitsumi".
> On page 33, replace the second paragraph of
the second list entry with the following:
When the Update Windows desktop when WIN-OS/2
desktop is modified option is selected during
the installation, the WIN-OS/2(*) PROGMAN.INI
file points to the Microsoft(**) Windows(**)
group files. However, WIN-OS/2 does not use
the Microsoft Windows PROGMAN.INI file. Two
different PROGMAN.INI files exist and each one
is maintained by the respective system (OS/2
or Windows).
Because both desktops share group files, they
will reflect the changes when an existing
group of files is modified. However, if a
modification to the PROGMAN.INI file is
necessary (add/remove a group file), the
desktops will differ. New groups will not be
reflected on the Microsoft Windows desktop.
CHAPTER 3. ADDING OS/2 2.1 TO A DOS SYSTEM (DUAL
_________________________________________________
BOOT)
_____
> On page 37, add the following warning after
the first paragraph:
Warning: While it is possible to install OS/2
2.1 and DOS in the same partition, you might
experience problems during the installation.
To avoid these problems, use Boot Manager
instead of Dual Boot. Refer to Chapter 4,
"Installing Multiple Operation Systems (Boot
Manager)" for more information.
> On page 48, replace the boxed note with the
following:
+--- What to Do if Dual Boot Does Not Work --+
| |
| If the BOOT command is unsuccessful when |
| you try to switch from DOS to OS/2 2.1, |
| you might have one or more active |
| terminate-and-stay-resident (TSR) or DOS |
| cache programs. If so, end the programs |
| before you use the BOOT command. For TSR |
| programs that are loaded from |
| AUTOEXEC.BAT, you must deactivate the |
| programs before using the BOOT command. |
| |
+--------------------------------------------+
CHAPTER 4. INSTALLING MULTIPLE OPERATING SYSTEMS
_________________________________________________
(BOOT MANAGER)
______________
> On page 50, add the following note after the
first paragraph:
Note: If you have a system with a VESA(**)
SUPER I/O controller and two disk
drives, the system will not start DOS
from the Boot Manager menu. Instead,
it will display a non-system disk or
disk error message. For more
information on this message, check the
VESA controller documentation or
contact the manufacturer.
> On page 52, add the following note after the
third paragraph:
Note: If a partition is going to contain an
operating system, the partition cannot
be larger than 1 GB (gigabyte) or 1024
cylinders.
> On page 70, replace the table entry for OS/2
2.1 with the following:
+----------+------------+------------------------+
| OS/2 2.1 | 20-40MB | (For operating system) |
| | | |
| | Minimum of | (For swapper file) |
| | 10MB | |
| | | (For multimedia |
| | 5MB | support) |
| | | |
| | | OS/2 2.1 can be in a |
| | | primary partition or |
| | | logical drive. If you |
| | | choose a minimum size |
| | | for the partition, you |
| | | might want to place |
| | | the swap file on |
| | | another partition. To |
| | | do this, select Select |
| | | features and install |
| | | from the OS/2 Setup |
| | | and Installation |
| | | window. Then, select |
| | | Software |
| | | configuration. You |
| | | can also install the |
| | | WIN-OS/2 support in |
| | | another partition. To |
| | | do this, select |
| | | WIN-OS/2 Support and |
| | | its associated More |
| | | push button from the |
| | | OS/2 Setup and |
| | | Installation window. |
| | | |
| | | If you want to install |
| | | all features and you |
| | | want the swap file on |
| | | the same partition, |
| | | consider making the |
| | | OS/2 partition larger. |
+----------+------------+------------------------+
> On page 83, add the following section before
the section titled "Bypassing the Boot Manager
Menu":
Installing the Upgraded Version of MS-DOS 6.x
If you are running a Dual Boot or Boot Manager
configuration and you want to install the
upgraded version of MS-DOS(**) 6.x, do the
following:
1. Start your system with a current version
of MS-DOS using a bootable MS-DOS
diskette; do not use a Dual Boot or Boot
Manager session.
2. Prepare an Uninstall Diskette so you can
restore your previous version of DOS if
needed. (Refer to your MS-DOS
documentation for instructions.)
3. Edit the CONFIG.SYS and AUTOEXEC.BAT
files.
a. Type REM before each command line that
starts a disk-caching,
delete-protection, or antivirus
program.
Note: You need to disable the startup
command for the MS-DOS
SMARTDrive program.
b. Disable any automatic message service,
such as a network pop-up or a printing
notification that is displayed on your
screen.
c. Save your changes to the CONFIG.SYS
and AUTOEXEC.BAT files.
d. Restart your system with the current
installed version of MS-DOS, but not
from a Dual Boot or Boot Manager
session.
4. Insert the MS-DOS 6.x SETUP Diskette 1
into drive A.
5. At the DOS command prompt, type:
A:SETUP
6. If your system is setup to use OS/2 Boot
Manager, you will receive a message that
states "This partition will not be
available when using MS-DOS 6.x." Ignore
this message and choose Continue Setup.
If your system is setup to use OS/2 Dual
Boot, you will receive a message prompting
you to remove the non-MS-DOS operating
system files from the drive. Ignore this
message and choose Do Not Remove the
Files. You will also receive a message
stating "The operating system on the drive
may be disabled." Ignore this message and
choose Continue Setup.
7. Follow the instructions on your screen.
If you need help during any of these
procedures, press F1 for Help.
8. When you are prompted to do so, insert the
diskette created in step 2 into drive A.
9. Restart your system when you have
completed the Setup program. The system
should start in MS-DOS 6.x.
Warning: The MS-DOS 6.x installation
program suggests that you run the
MS-DEFRAG and MS(**) DOUBLE SPACE utility
programs. These utility programs are not
compatible with the OS/2 environment, and
might cause data loss in OS/2 if executed.
Other MS utility programs that perform
direct diskette I/O, such as Interlink and
UNDELETE, could compromise the OS/2 file
system and are not supported.
10. To make the OS/2 system partition active
again:
o If your system is setup to use OS/2
Boot Manager, do the following:
a. Type FDISK at the command prompt.
b. When the FDISK screen appears,
choose option 2; then press Enter.
c. Choose the number that corresponds
with the Boot Manager partition;
then press Enter.
d. When the confirmation screen
appears, press Esc.
e. Press Esc again to exit FDISK.
f. Restart your system.
o If your system is setup to use OS/2
Dual Boot, copy the COMMAND.COM file
from the \DOS directory to the root
directory.
Note: SETUP places your previous DOS files in
a directory named OLD_DOS.x. If you
are sure you do not want to restore
your previous version of DOS, you can
delete the directory and its contents
by typing DELOLDOS at the command
prompt.
CHAPTER 5. USING A RESPONSE FILE TO INSTALL
____________________________________________
> On page 87, replace the instructions after the
first paragraph with the following:
This procedure requires unpacking compressed
files. To do this, copy the UNPACK2.EXE file
from Diskette 2 to your hard drive. Any
unpack instructions should be performed from
this hard drive.
1. Make a copy of Diskette 1. You will
modify only this copy.
2. Make extra room on the copy of Diskette 1
by deleting the following files, which
will not be needed in a response file
installation:
a. Delete the MOUSE.SYS, SYSINST2.EXE,
and BUNDLE files from the copy of
Diskette 1.
Note: Deleting the BUNDLE file is not
necessary for CD-ROM
installation.
b. If you are installing OS/2 2.1 on a
Micro Channel(*) computer, delete the
IBM1*.ADD file from the copy of
Diskette 1.
c. If you are installing OS/2 2.1 on a
non-Micro-Channel computer, delete the
IBM2*.ADD and *0S.SYS files from the
copy of Diskette 1.
3. Edit the CONFIG.SYS file on the copy of
Diskette 1:
a. Change the SET OS2_SHELL statement
from "SET OS2_SHELL=SYSINST2.EXE" to
the following:
SET OS2_SHELL=RSPINST.EXE A:\OS2SE20.RSP
b. Delete the following statement:
DEVICE=MOUSE.SYS
c. If you are installing OS/2 2.1 on a
Micro Channel computer, delete the
following statements in the CONFIG.SYS
file on the copy of Diskette 1:
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM1S506.ADD
d. If you are installing OS/2 2.1 on a
non-Micro-Channel computer, delete the
following statements in the CONFIG.SYS
file on the copy of Diskette 1:
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM2ADSK.ADD
BASEDEV=IBM2SCSI.ADD
4. Use the following statement to unpack the
compressed file REQUIRED that is located
on Diskette 11 and copy the SAMPLE.RSP
file contained within it to the root
directory of your hard drive:
UNPACK2 A:\REQUIRED C:\ /N:SAMPLE.RSP
a. Use an editor (such as the System
Editor) to modify and save the file.
The file contains comments that
explain each of the installation
options.
b. Copy this modified response file to
the copy you made of Diskette 1 and
rename it OS2SE21.RSP. For example:
COPY C:\SAMPLE.RSP A:\OS2SE21.RSP
5. Use the following statement to unpack the
compressed file REQUIRED that is located
on Diskette 7 and copy the RSPINST.EXE
file contained within it to the root
directory of your hard drive:
UNPACK2 A:\REQUIRED C:\ /N:RSPINST.EXE
6. Copy the RSPINST.EXE file to the copy of
Diskette 1.
7. If you have a Micro Channel computer and
the Reference Diskette contains ABIOS.SYS
and *.BIO files, you will also need to
modify the Installation Diskette:
a. Make a copy of the OS/2 2.1
Installation Diskette.
b. Delete the *.BIO and ABIOS.SYS files
from the copy of the Installation
Diskette.
c. Copy the *.BIO and ABIOS.SYS files
from the Reference Diskette to the
copy of the Installation Diskette.
Note: This Installation Diskette copy
is now system-specific. You
will need to create a modified
Installation Diskette for each
type of system on which you are
installing OS/2 2.1.
d. Use this copy of the diskette during
the installation process.
8. Begin the installation of the workstation
by inserting the copy of the Installation
Diskette and restarting the system.
9. When prompted for Diskette 1, insert the
modified copy of Diskette 1 and press
Enter.
From this point, the installation program
will prompt only for the insertion of
diskettes. No other installation actions
are necessary.
10. When prompted to insert Diskette 1 again,
insert the original copy of Diskette 1
into drive A.
Note: If you are installing from diskettes,
you will be prompted to insert the
Installation Diskette after the display
driver diskettes; insert Diskette 1
instead.
Response files can be used to install the same
set of options on multiple workstations. You
must ensure that the workstations are set up
with the same set of options and hardware.
> On page 88, add the following after the first
paragraph under the section titled "Installing
OS/2 2.1 from a Local Area Network Source":
Requirements for remote installation of OS/2:
o The RAM requirements vary from 6MB to 10MB
or more, depending on the installation
variables.
-- Redirected remote installation
requires more RAM than disk
installation because the SWAPPER.DAT
file is not active.
-- If you are doing a redirected remote
installation without CID, you only
need about 6MB of RAM.
-- When using CID, the RAM requirements
usually range from 6MB to 8MB.
-- If you are using a process on top of
CID, like NVDM/2, 8MB to 10MB (or
more) might be required. The main
variable with CID is the size of the
REXX procedure and which dynamic link
libraries it pulls in. With remote
installation, the LAN connection
utility programs are the main
variables. The version of OS/2 that
you are installing is another
variable.
-- The reduced diskette version of OS/2
2.1 (20 diskettes) requires more RAM
because of the new UNPACK2.EXE
routine.
o During remote installation, the
SWAPPER.DAT file is not active because the
disk partition containing the active
swapper file cannot be formatted during
installation. The SWAPPER.DAT file can be
made active, but the disk partition has to
be a local partition and preformatted. In
order to activate the SWAPPER.DAT file,
the CONFIG.SYS file has to be edited. To
do this, replace the existing
MEMMAN=NOSWAP statement with the
following:
MEMMAN=SWAP,PROTECT
SWAPPATH=D:\ 2048 4096
o Personal Computers might require more RAM
as the network drivers might have to store
more data into the RAM buffers until the
processor is able to handle the data.
APPENDIX A. ADDING FEATURES AND CHANGING YOUR
______________________________________________
SYSTEM CONFIGURATION
____________________
> On page 107, add the following note before the
section titled "Description of the System
Configuration Choices":
Note: Make sure that the same diskettes used
for the installation of OS/2 2.1 are
used for Selective Install. There are
two levels of diskettes, compressed and
uncompressed. These diskettes are
identical except for the purpose of
Selective Install. The compressed
diskettes have salmon-colored labels,
and the uncompressed diskettes have
blue-colored labels.
> On page 114, add the following note after the
heading titled "Installing Display Drivers
Using Display Install":
Note: If you want to install display drivers
using Display Install, you must have
OS/2 DOS Support installed.
APPENDIX B. DIAGNOSING SYSTEM PROBLEMS
_______________________________________
> On page 117, replace the first list entry with
the following:
o Single inline memory modules conflicts
You might encounter problems if the single
inline memory modules of your computer
system were produced by different
manufacturers, are of different classes,
or operate at different speeds. Refer to
the TRAP0002 message for more information.
> On page 118, add the following after the last
list entry:
o Disk Read Error
Systems with a HYPERACE(**) 486 Upgrade
might receive a "Disk Read Error" when
trying to read Diskette 1 during
installation. Several switches on the
HYPERACE card might need to be disabled:
1. Switch 1 - disables the main cache.
2. Switch 2 - disables the HIMEM cache.
3. Switch 4 - disables the BIOS cache.
After installation, reset the switches to
enable the caches.
For more information on the procedures,
check the HYPERACE card documentation.
> On page 119, replace the line "Messages
beginning with "TRAP"" with the following:
Messages beginning with "TRAP0002"
> On page 121, add the following messages:
+--------------------------------------------+
| |
| An error occurred when System Installation |
| tried to locate the KBD01.SYS file. |
| |
+--------------------------------------------+
Explanation: The installation program could
not locate the KBD01.SYS file on a system
with a Micropolis(**) SCSI hard drive. This
file is not located in the default path or
the path specified in the CONFIG.SYS file.
Action:
(1) Edit the CONFIG.SYS file and add the
following statement:
DEVICE=KBD01.SYS
(2) Disable the "Read ahead cache" in the
UTIL.EXE.
+--------------------------------------------+
| |
| An error occurred when System Installation |
| tried to load the dynamic link library. |
| |
+--------------------------------------------+
Explanation: The installation program could
not load the dynamic link library because
there is not enough random access memory
(RAM).
Action: Add more system memory (RAM).
+--------------------------------------------+
| |
| A disk read error occurred. |
| |
+--------------------------------------------+
Explanation: The BIOS level of the Future
Domain(**) adapter is not compatible.
Action: Contact Future Domain for a BIOS
upgrade if you own:
o Future Domain TMC-850/860/875/885 with
BIOS revision level 7.0.
o Future Domain TMC-1660/1670/1680 with
BIOS revision level 2.0.
> On page 122, replace the COUNTRY.SYS message
with the following:
+--------------------------------------------+
| |
| COUNTRY.SYS file cannot be found |
| |
+--------------------------------------------+
Explanation: The OS/2 operating system does
not recognize the hard disk or diskette.
(1) If you have a PS/2(*) P70, you need to
request an engineering change.
(2) A diskette drive or a hard disk drive
controller might have an additional device
(such as a tape backup) attached to it.
(3) The diskette drive or hard disk drive
controller might not reside at its own
interrupt request (IRQ) level.
(4) The hard disk partition on which you are
installing OS/2 2.1 was compressed with a
DOS data compression program.
(5) If you have a Gateway(**) Nomad(**)
laptop computer with Phoenix(**) BIOS 1.02,
you will have to update the BIOS to the next
level.
(6) If your system is using an AMI(**) Fast
Disk or a Fast Disk II SCSI adapter, they
will be recognized as Adaptec adapters.
(7) You have more than two (2) hard drives
in the system.
Action:
(1) Contact your IBM customer engineer or
computer dealer and request the engineering
change announcement "ECA068."
(2) Disconnect the device, if possible.
(3) Refer to the operations manual that came
with your computer for information about the
IRQ setting. (Refer to OS/2 2.1 Using the
Operating System for more information about
setting IRQ levels.)
(4) Use the data compression program to
decompress the partition, and then retry the
installation.
(5) Update your Gateway Nomad Laptop
computer with Phoenix BIOS 1.03 or later.
(6) After installation, edit the CONFIG.SYS
file as follows:
o Delete any line with the following:
BASEDEV=AHA1xxx.ADD
where xxx can be any character.
o Ensure that the statement
BASEDEV=IBMINT13.I13 is included.
(7) Check the partitions on any drives
beyond the first two drives. If they are
primary partitions, back up the data and
re-partition them as logical drives.
> On page 123, replace the TRAPxxx message with
the following:
+--------------------------------------------+
| |
| TRAPxxx |
| |
+--------------------------------------------+
Explanation: In general, traps are symptoms
of software-related problems. After you
have pursued these symptoms from a software
failure perspective, you should consider the
potential of a hardware cause relating to
caches and memory.
(1) If your computer has an 80486
microprocessor, your computer might require
faster RAM chips (60ns or 70ns).
(2) There might be a problem with the
external (level 2) CPU memory cache or main
memory system on ISA or EISA systems.
Action:
(1) From the setup/diagnostics diskette or
the BIOS Setup program built into the
computer, try disabling all shadow RAM and
external (level 2) CPU memory cache.
(2) If problems persist during the
installation of OS/2 after performing the
above action, turn off the turbo switch (if
one is available) on your system and retry
the operation. Disable caching during
installation or turn the turbo switch off.
> On page 123, add the following messages:
+--------------------------------------------+
| |
| TRAP0002 |
| |
+--------------------------------------------+
Explanation: A TRAP0002 error can be a
memory parity error on the system board or
on an adapter card.
(1) Your computer system might have single
inline memory modules that were produced by
different manufacturers or that operate at
different speeds. Or, your computer system
might have different classes of single
inline memory modules. (For example, a 1x9
module cannot be used with a 1x3 module.)
Action:
(1) Remove any defective single inline
memory module. It might also be necessary
to replace one or more modules.
(2) If your IBM computer is a 33 MHz and the
microprocessor card part number is 84F9356,
contact your local IBM representative and
request an ECA053.
(3) If the Memory Riser card part number is
N33F4905 or 84F9356 on an IBM Model 8590
system, contact your local IBM
representative and request an ECA084.
+--------------------------------------------+
| |
| SYS0005 |
| |
+--------------------------------------------+
Explanation: When trying to do a redirected
remote installation of OS/2 2.1 using
SYSINST2 for panel installation, the error
message SYS0005 appears while attempting to
copy UNPACK.EXE.
Action: This Access Denied Error is caused
by damage to the extended attribute data on
the NetWare(**) Server. To correct this
problem, delete the old disk images on the
server and create new OS/2 disk images.
> On page 124, add the following message:
+--------------------------------------------+
| |
| SYS1719 |
| |
+--------------------------------------------+
Explanation: The file IBM386FS\HPFS386.IFS
does not contain a valid device driver or
file system driver.
Action: Edit your CONFIG.SYS file and
delete the following line:
IFS=x:\OS2\HPFS.IFS
> On page 124, replace the SYS2025 message with
the following:
+--------------------------------------------+
| |
| SYS2025 |
| |
+--------------------------------------------+
Explanation: A disk read error occurred.
This might be a disk error or a damaged
system boot record.
Action:
(1) If this error occurred while the system
was loading, follow the procedure under
"Recovering from Errors on the Hard Disk".
(2) If this error occurred when the system
was reading the installation diskettes,
there might be an error on the diskette. If
you already have an operating system
installed on your computer, use the DISKCOPY
command to make a copy of the installation
diskettes. Retry the installation with the
newly copied diskettes.
(3) If your computer has BIOS supplied by
AMI or Phoenix, you might need to upgrade
the BIOS. Refer to Appendix G.
(4) If your system has a local bus IDE
controller card, disable the BIOS on the
32-bit local bus IDE controller card and use
the generic INT13 driver instead of
IBM1S506.ADD.
(5) Make sure that there is not a hardware
problem with your hard disk controller or
your diskette drive.
> On page 125, replace the SYS2026 message with
the following:
+--------------------------------------------+
| |
| SYS2026 |
| |
+--------------------------------------------+
Explanation: The file OS2LDR cannot be
found. This is a hidden system file and
must reside in the root directory of the
drive from which the operating system is
started.
Action:
(1) Make sure a non-system diskette is not
in the diskette drive. If necessary, remove
the non-system diskette and restart the
system.
(2) If the OS2LDR file is missing from the
hard disk, start up the system using the
Installation Diskette. Insert Diskette 1
and press Enter.
(3) Copy the OS2LDR file from the
Installation Diskette to the OS/2 partition.
> On page 127, add the following after the
paragraph under the heading titled Diskette 1:
If you are installing on a system with an
Allways(**) IN2000 SCSI adapter, an IPE or
FDISK error is displayed during the
installation of Diskette 1. Upgrade your
system to the current BIOS level of VCN:1-02.
The Allways IN2000 SCSI adapter might require
an EPROM upgrade to operate with OS/2 2.1.
You might find that you have some problems
when trying to install over DOS partitions.
To correct these problems, you need to install
the EPROMS and reformat the hard drive.
If you are installing OS/2 2.1 on a MYLEX
system, a TRAP0008 error occurs during the
installation of Diskette 1. For more
information on this error, contact MYLEX.
If you are installing on a Compaq(**) 386/331
Deskpro system, a TRAP000D error occurs during
the installation of Diskette 1. To correct
this problem, do the following:
1. Make a copy of Diskette 1. You will
modify the copy.
2. Use an editor to edit the CONFIG.SYS file
that exists on the copy of Diskette 1.
3. Delete the following statements:
BASEDEV=IBM2M57.ADD
BASEDEV=IBM2SCSI.ADD
4. Use the copy of the diskette during the
installation process instead of the
original.
> On page 127, add the following list entry
after Diskette 3:
o Diskette 6
If the system refuses Diskette 6 and makes
a beeping sound, your system might be
infected with the Joshi virus. The Joshi
virus is a DOS virus that interferes with
OS/2 and seems to cause random lockups.
The Joshi virus:
-- Operates by trapping disk reads and
writes. If the virus is active in
memory, programs that try to locate
the virus on diskette will have
problems detecting it.
-- Is carried on the boot sector of an
infected data diskette or system
diskette. This virus originated in
DOS but can survive in OS/2. When you
start an infected system, the virus
resides in memory and survives a
Ctrl+Alt+Del startup. If the user
does not type in the text "Happy
Birthday Joshi", the system will stop.
-- Is copied to the boot sector of every
diskette. The virus will be
transferred to any computer on which
the user performed any diskette
operation that included reading from,
or writing to, the infected diskette.
-- Spreads from infected diskettes to DOS
and OS/2 systems when the systems are
started from diskettes.
-- Interferes with the startup from the
hard disk of OS/2-based systems. The
warning that OS/2 will give is that
the IBM1FLPY.ADD file is bad or
missing.
Many antivirus packages are effective at
detecting this virus. In DOS, The Norton
Antivirus(**) Version 2.1 can both detect
and clear the virus. The Joshi virus can
also be cleared from DOS-based systems
with the undocumented FDISK parameter MBR.
However, the FDISK.EXE must be copied to
and run from each partition. Type the
following:
FDISK /MBR
This procedure causes the master boot
record to be refreshed by the system, and
the Joshi virus is overwritten. However,
this procedure does not remove the virus
from memory. The system needs to be
restarted and rescanned for the virus.
In OS/2, Central Point(**) Antivirus can
detect the virus. McAfee(**) Clean and
Scan can both detect and clear the virus.
For more information on this antivirus
program, contact McAfee Associates at
(408) 988-3832.
> On page 127, add the following to the end of
the page:
Installation on a Quantum II XL Hard Card
If you have a Quantum(**) hard card, you must
make a modification to the
BASEDEV=IBM1S506.ADD line in the CONFIG.SYS
file. To modify the BASEDEV statement, do the
following:
1. Edit the CONFIG.SYS file on Diskette 1.
2. Change the BASEDEV statement to:
BASEDEV=IBM1S506.ADD /A:1 /IRQ:11
3. Save the CONFIG.SYS file.
4. Install OS/2 2.1.
(These are the default settings for the
Quantum hard card.)
Black Lines on a OS/2 Logo Screen
During the installation on a Gateway 2000 with
an 80486/66MHz processor, a local bus, and an
ATI Graphics Ultra Pro, the system will get to
the screen with the colorful OS/2 full-screen
symbol, and then the installation will stop.
The display screen shows horizontal bands of
video separated by black bands that scroll
horizontally across the screen. To correct
this problem, do the following:
1. Start DOS.
2. Change the OS/2 directory to MACH32.
3. Type:
INSTALL
4. At the Main Selection screen select Set
Power up Configuration.
5. Select Monitor Type, and press Enter.
6. Select 1572 Monitor with 72Hz Refresh
Rate, and press Enter.
7. Select IBM Default as the new display.
Note: After OS/2 is successfully installed,
repeat the steps to reselect the 1572
Monitor type.
White Screen Appears during Installation
If the display screen is white during the
installation of OS/2 2.1 and there is no
system activity, set the video adapter to
operate on an 8-bit mode and move the adapter
to an 8-bit slot. Do the following:
1. Turn off the system and disable the
autosensing capability of the video
adapter.
2. To modify the settings, refer to the
documentation that came with your video
adapter.
3. Place the adapter in an 8-bit slot until
you have successfully installed OS/2 2.1.
4. The adapter can be returned to the 16-bit
slot and set back to the 16-bit mode.
> On page 128, add the following to the list
entries:
o System is unable to access the CD-ROM
drive
o Redirection of XGA$DMQS Directory is
ignored
o An error appears when using Dual Boot
o White screen or blank screen after
installation
o OS/2 2.0 desktop does not migrate
o Slow SCSI support
o System will not start DOS
> On page 129, add the following after the
section titled "Adding Support for a Mouse":
System Unable to Access CD-ROM Drive
If you clicked on the CD-ROM check box on the
System Configuration screen during the
installation of OS/2, the installation program
put the entry None in the CD-ROM text box and
the CD-ROM files were not copied.
Because some drives are not directly supported
by the device drivers shipped with the OS/2
product, you must now select OTHER from the
selection list to enable CD-ROM support.
For Sony, Mitsumi, or Hitachi(**) users, if
you cannot access your CD-ROM drive, restart
your system and do the following:
1. Copy the following files from Diskette 1
to the hard disk:
COPY A:\OS2CDROM.DMD C:\OS2
COPY A:\CDFS.IFS C:\OS2
2. Edit your CONFIG.SYS file on the hard disk
and add the following statements:
DEVICE=C:\OS2\OS2CDROM.DMD /Q
IFS=C:\OS2\CDFS.IFS /Q
3. Perform a shutdown and restart the system.
For Sound Blaster users with the device driver
SBPCD2.SYS, if you cannot access your CD-ROM
drive, restart your system and do the
following:
1. Copy the following file from Diskette 1 to
the hard disk:
COPY A:\CDFS.IFS C:\OS2
2. Edit the CONFIG.SYS file on the hard disk
and add the following statement:
IFS=C:\OS2\CDFS.IFS /Q
3. Restart your system to OS/2.
4. Start the Selective Install program in the
System Setup folder.
a. Click on the CD-ROM Device Support
check box on the System Configuration
screen.
b. Click on OK to display the CD-ROM
selection list. Scroll to the bottom
of the list, select the choice OTHER
and click on OK.
5. Continue the Selective Install process
until completed.
6. Edit the CONFIG.SYS file and delete the
following line:
REM DEVICE=C:\OS2\OS2CDROM.DMD /Q
7. Perform a shutdown and restart the system.
> On page 130, add the following before the
section titled "Problems with a Mouse Not
Working":
Redirection of XGA$DMQS Directory Ignored
during Installation
The installation program copied the XGA$DMQS
files to the same partition as the operating
system. To correct this problem, do the
following:
1. XCOPY the XGA$DMQS directory from the
drive containing OS/2 2.1 to the
redirected drive.
a. Start an OS/2 session.
b. Type XCOPY C:\XGA$DMQS D:\XGA$DMQS /S
(where C is the drive containing OS/2
2.1 and D is the redirected target
drive)
c. Press Enter.
2. Edit the C:\CONFIG.SYS file.
3. Add the following line to the file:
SET DMQSPATH=D:\XGA$DMQS
4. Save the changes and exit the editor.
5. Perform a shutdown and restart the system.
> On page 131, add the following sections before
the section titled "LOGO Screen Problems":
Mouse Not Working after Selective Install
If you did a selective installation of a new
mouse and the mouse is not working, you will
need to edit your CONFIG.SYS file. To edit
the CONFIG.SYS file, do the following:
1. Open OS/2 Window.
2. Type:
e config.sys
and press Enter.
3. Delete the mouse device driver statements.
For example:
DEVICE=C:\OS2\MOUSE.SYS
Note: If your mouse device driver is not
for a Microsoft or PS/2 mouse, you
might have two DEVICE= statements
to delete.
4. Save the file.
o Pull-down the File menu by pressing
F10 and then Enter.
o Select Save As.
o Type in the CONFIG.SYS file name and
press Enter.
5. Exit the System Editor by pressing Alt+F4.
6. Shut down and restart the system.
Error When Using Dual Boot on a PS/1 System
On PS/1(*) systems preinstalled with DOS 5.0,
using Dual Boot from OS/2 to DOS results in an
error. To correct this problem, press and
hold Ctrl+Alt, and press Del to restart the
system.
> On page 132, change the heading to "White
Screen or Blank Screen Problems" and add the
following information after the first
paragraph:
On restarting the system after the complete
installation of OS/2, the desktop appears to
be blank. If the display screen is blank,
performing CHKDSK on the drive connected to
the ProComm(**) Micro Channel SCSI adapter
might result in the system not working. To
correct this problem, contact ProComm to
receive the device driver needed for the SCSI
card.
> On page 132, add the following section before
the section titled "Making the Boot Manager
Startable":
The OS/2 2.0 Desktop Does Not Migrate After
OS/2 2.1 Installation
After you install OS/2 2.1, you might have
some problems migrating the OS/2 2.0 desktop.
o If you have a desktop problem, do the
following:
1. Insert the Installation Diskette and
turn on the computer.
2. Insert Diskette 1
3. Press Esc at the Welcome screen to get
to the command prompt.
4. Delete the DESKTOP directory.
5. Restart the system; the desktop should
be re-created.
6. If the problem continues, you must run
the MAKEINI program.
o If you have moved program groups off the
desktop and into a folder, you should move
them back on the desktop before installing
OS/2 2.1. Otherwise, duplicate icons
could appear on the screen. If you try to
delete these icons, the original icons
will also be deleted.
o If you want to recover a backed up OS/2
2.0 desktop, you can use the following
procedure:
1. Insert the Installation Diskette, and
turn on the computer.
2. Press Esc to get to the command
prompt.
3. Delete or rename the INI files on the
hard disk.
4. Copy the backup INI files to the OS/2
subdirectory.
5. Run the MAKEINI OS2.INI INI.RC
program.
6. Run the MAKEINI OS2SYS.INI INISYS.RC
program.
7. Delete the DESKTOP directory.
8. Restart the system.
Notes:
1. If you try to recover the backed up
OS/2 2.0 desktop, the customization
for the OS/2 2.1 desktop will be lost.
2. The name of your DESKTOP directory
might be slightly different. To find
the actual name of your DESKTOP
directory currently in use, display
the Settings notebook for the desktop
and select the File page. The current
desktop name is shown under Physical
name.
> On page 133, add the following section before
the section titled "Existing Application Not
Migrated":
Slow SCSI Support or Missing Icons
After installation, slow SCSI support occurs.
In addition, evidence of data damage such as
missing icons might also occur.
Check the documentation for the hard drive and
the controller card to ensure that their
settings are both set for the ASYNCH mode or
the SYNCH mode.
> On page 133, add the following sections to the
end of the page:
System Will Not Start DOS from the Boot
Manager Menu
On a system with a VESA SUPER I/O controller
and two disk drives, the system will not start
DOS from the Boot Manager menu. It will
display a non-system disk or disk error
message.
For more information on this message, check
the VESA controller documentation or contact
the manufacturer.
Running CHKDSK
To run CHKDSK /F using diskettes:
1. Insert the Installation Diskette into
drive A.
2. Turn on the computer. If the computer is
already on, press and hold Ctrl+Alt, and
press Del to restart the system.
3. When you are prompted to do so, remove the
Installation Diskette and insert Diskette
1.
4. Press Enter.
5. When the Welcome screen is displayed,
press Esc to display the command prompt.
6. Remove Diskette 1 and insert Diskette 2.
Type:
CHKDSK C: /F
and press Enter.
Note: If your operating system resides on
a drive other than C, use the
appropriate drive letter instead.
> On page 137, add the following to the end of
item 7:
To run CHKDSK from a CD-ROM:
1. Insert the Installation Diskette into
drive A.
2. Shut down and restart the system.
3. When prompted to do so, remove the
Installation Diskette and insert Diskette
1; then press Enter.
4. When prompted to do so, insert the CD in
the CD-ROM drive, and then press Enter.
5. When the Welcome screen is displayed,
press Esc to display the command prompt.
6. To change directories, type:
CD\
and press Enter.
7. Type:
CD OS2SE2
and press Enter.
8. Type:
CD DISK_2
and press Enter.
9. Type:
CHKDSK x: /F
(where x is the drive letter of your OS/2
system partition) and press Enter.
APPENDIX F. MIGRATING FROM OS/2 EXTENDED EDITION
_________________________________________________
TO OS/2 2.1
___________
> On page 166, add the following note to the end
of the page:
Note: If you are installing OS/2 2.1 on a
system with a LAN SERVER 3.0 and a
HPFS386, you will get a SYS1719 error
message. Refer to the "SYS1719"
message for more information.
APPENDIX G. UPGRADING THE BIOS OF YOUR COMPUTER
________________________________________________
> On page 167, replace the sentence about
Phoenix BIOS with the following:
For questions about products that use Phoenix
BIOS, call the computer manufacturer directly.
If there are additional questions, call
Phoenix at (714) 440-8080.
APPENDIX H. NOTICES
____________________
> On page 171, add the following new appendix:
Note: "Notices" will then become Appendix I.
Appendix H. Creating an OS/2 Startup Diskette
The following procedure explains how to create
a startup diskette for OS/2 2.1.
1. Insert the Installation Diskette into
drive A.
2. Copy the SYSINSTX.COM file to your OS/2
directory.
3. Remove the Installation Diskette from
drive A.
4. Insert Diskette 1 into drive A.
5. Copy the KEYBOARD.DCP and SYSINST1.EXE
files to a subdirectory on your hard disk.
6. Use the ATTRIB command to display the
OS2KRNL, OS2LDR, and OS2LDR.MSG files.
7. Remove Diskette 1 from drive A.
8. Insert a blank, formatted diskette into
drive A and type:
SYSINSTX A:
9. Copy the OS2KRNL, OS2LDR, and OS2LDR.MSG
files to the startup diskette, and then
use the ATTRIB command to hide the files.
10. Copy the KEYBOARD.DCP and SYSINST1.EXE
files from the subdirectory to the startup
diskette.
11. Copy the following libraries from the
\OS2\DLL directory to the startup
diskette:
ANSICALL.DLL DOSCALL1.DLL
NLS.DLL NPXEMLTR.DLL
BKSCALLS.DLL KBDCALLS.DLL
OS2CHAR.DLL BMSCALLS.DLL
MOUCALLS.DLL QUECALLS.DLL
BVHINIT.DLL MSG.DLL
SESMGR.DLL BVSCALLS.DLL
NAMPIPES.DLL VIOCALLS.DLL
12. Copy the HARDERR.EXE and COUNTRY.SYS files
from the \OS2\SYSTEM directory to the
startup diskette.
13. Copy the SYSLEVEL.OS2 file from the
\OS2\INSTALL directory to the startup
diskette.
14. Copy the CMD.EXE, DOS.SYS, IBMINT13.I13,
and OS2DASD.DMD to the startup diskette
from the \OS2 directory. If you are
planning to use HPFS, you need to copy the
HPFS.IFS file to the startup diskette.
15. If you have an AT(*) system, copy the
CLOCK01.SYS, KBD01.SYS, PRINT01.SYS,
SCREEN01.SYS, and IBM1FLPY.ADD files to
the startup diskette.
16. If you have a Micro Channel PS/2 system,
copy the CLOCK02.SYS, KBD02.SYS,
PRINT02.SYS, SCREEN02.SYS, and
IBM2FLPY.ADD files to the startup
diskette. The following command is used
to copy the ABIOS.SYS file on the startup
diskette for a PS/2 system:
ECHO . > A:ABIOS.SYS
17. If you have a SCSI hard drive, copy the
IBM2SCSI.ADD file (or the .ADD file from
the manufacturer). If you have a hard
drive other than a SCSI hard drive, copy
the IBM1S506.ADD file to the startup
diskette.
18. Using an editor, create the following
CONFIG.SYS file on the startup diskette
(in this case, for HPFS):
IFS=HPFS.IFS /CACHE:64
BUFFERS=32
IOPL=YES
MEMMAN=NOSWAP
PROTSHELL=SYSINST1.EXE
SET OS2_SHELL=CMD.EXE
DISKCACHE=64,LW
PROTECTONLY=YES
LIBPATH=.;\;
PAUSEONERROR=NO
CODEPAGE=850
DEVINFO=KBD,US,KEYBOARD.DCP
DEVICE=\DOS.SYS
SET PATH=.;\
SET DPATH=\;
SET KEYS=ON
BASEDEV=PRINT0x.SYS (where x is 1 for AT; 2 for Micro Channel
BASEDEV=IBMxFPLY.ADD (where x is 1 for AT; 2 for Micro Channel
BASEDEV=IBMINT13.I13
BASEDEV=OS2DASD.DMD
a. If you have a SCSI drive on a Micro
Channel computer, add the following
statement to this file:
BASEDEV=IBM2SCSI.ADD
b. If you have a hard drive other than a
SCSI drive on a non-Micro Channel
computer, add the following statement
to this file:
BASEDEV=IBM1S506.ADD
c. If you have any space left on your
diskette, copy the CHKDSK.COM file
from the \OS2 directory to the startup
diskette.
PART 2: CHANGES TO OS/2 2.1 USING THE OPERATING SYSTEM
Part 2 contains information that is new or
different from the information in the OS/2 2.1
Using the Operating System book.
The chapter numbers and titles in this booklet are
the same as those used in the Using the Operating
System book; only those chapters of the Using book
that are changed are included here.
ABOUT THIS BOOK
_______________
> On page xxvi, replace the last three entries
of the list in the section titled "How This
Book is Organized" with the following list
entries:
o Appendix A describes the keys and mouse
actions used in tasks.
o Appendix B contains some of the most
common error messages.
o Appendix C describes how to back up and
restore the desktop.
o Appendix D describes the OS/2 file
systems.
o Appendix E describes the file locations.
o Appendix F describes how to remove
programs.
o Appendix G contains forms for recording
information about your computer.
o Appendix H contains warranty and service
information for the mini-applications and
productivity aids.
o Appendix I describes the Memory Dump
process.
o Appendix J contains the trademarks and
service marks.
o Glossary of the terms used in this book.
o Index.
NEW FEATURES IN OS/2 2.1
________________________
> On page xxx, replace the list entry "The
Ultimotion(*) software motion video formats"
with the following:
o Ultimotion and Video software motion video
formats
CHAPTER 1. GETTING STARTED WITH OS/2 2.1
_________________________________________
> On page 23, add the following instructions at
the end of the section titled "Renaming an
Object":
You can also change the object name
by performing the following steps:
1. Select the object whose name you
want to change.
2. Press Shift+F9.
3. Type the new name in the Title
field.
4. Press the Enter key on the
numeric key pad.
Note: Press Ctrl+Shift+Enter
for any computer that
does not have a numeric
keypad.
> On page 40, replace the first set of lockup
instructions in the section titled "Locking Up
Your System" with the following:
To lock your system manually:
1. Point to an empty area on the
desktop.
2. Click mouse button 2.
3. Select Lockup now. If this is
the first time you have locked
up the keyboard, a window
appears where you can set up a
password. (You will use this
password later to unlock the
keyboard so that you can use the
computer.)
4. Type your password.
5. Carefully type your password
again for verification.
Note: If you forget your password, you must
turn the computer off and then on again
to unlock the keyboard. Any
information that was not saved before
the keyboard was locked will be lost.
First Edition (January 1994)
The following paragraph does not apply to the United Kingdom or any
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do
not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement may not apply to you.
This publication could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein;
these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time.
It is possible that this publication may contain reference to, or
information about, IBM products (machines and programs), programming,
or services that are not announced in your country. Such references
or information must not be construed to mean that IBM intends to
announce such IBM products, programming, or services in your country.
Requests for technical information about IBM products should be made
to your IBM authorized reseller or IBM marketing representative.
(C) Copyright International Business Machines Corporation 1994. All
rights reserved.
Note to U.S. Government Users -- Documentation related to restricted
rights -- Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.
---------------
(*) Trademark of the IBM Corporation.
(**) Trademark of Adaptec, Inc.
(*) Trademarks of the IBM Corporation.
(**) Docking Station is a trademark of NEC Home Electronics, Inc.
(**) ATI and Ultra are trademarks of ATI Technologies, Inc. Gateway 2000 is a
trademark of Gateway 2000, Inc. Sony is a trademark of Sony Corporation.
Panasonic is a trademark of Matsushita Electric Industrial Co., Ltd.
Mitsumi is a trademark of Mitsumi Denki Kabushki Kaisha.
(**) Media Vision and ProAudio Spectrum are trademarks of Media Vision, Inc.
Sound Blaster is a trademark of Creative Labs, Inc.
(*) Trademark of the IBM Corporation.
(**) Microsoft and Windows are trademarks of the Microsoft Corporation.
(**) VESA is a trademark of Video Electronics Standards Association.
(**) MS-DOS is a trademark of the Microsoft Corporation.
(**) MS is a trademark of the Microsoft Corporation.
(*) Trademark of the IBM Corporation.
(**) HYPERACE is a trademark of Hypertec Pty. Limited.
(**) Micropolis is a trademark of Micropolis Corporation. Future Domain is a
trademark of Future Domain Corporation.
(*) Trademark of the IBM Corporation.
(**) Gateway is a trademark of Gateway Systems Corporation. Nomad is a
trademark of Gateway 2000, Inc. Phoenix is a trademark of Phoenix
Technologies, Ltd. AMI is a trademark of American Megatrends, Inc.
(**) NetWare is a trademark of Novell, Inc.
(**) Allways is a trademark of Funk Software, Inc. Compaq is a trademark of
Compaq Computer Corporation.
(**) The Norton Antivirus is a trademark of Symantec Corporation.
(**) Central Point is a trademark of Central Point Software, Inc. McAfee is a
trademark of McAfee Associates. Quantum is a trademark of Quantum
Corporation.
(**) Hitachi is a trademark of Hitachi Ltd.
(*) Trademark of the IBM Corporation.
(**) ProComm is a trademark of Datastorm Technologies, Inc.
(*) Trademark of the IBM Corporation.
(*) Trademark of the IBM Corporation.
CHAPTER 4. SYSTEM SETUP
________________________
> On page 68, add the following note to the end
of the page:
Note: If the keyboard speed is set in
WIN-OS/2, when that WIN-OS/2 session is
started, the keyboard speed for the
entire system is reset and remains
reset even after that WIN-OS/2 session
is closed.
> Replace the Power section at the end of this
chapter with the information that follows.
POWER
The Power object manages and tracks power consumption in
battery-powered computers that support the Advanced Power
Management (APM) standard. The APM standard defines the
way the hardware and software work together to reduce
power consumption and help extend battery life.
If your computer supports the APM standard, the
Power object might be automatically installed
during the OS/2 2.1 installation process. If it
was not installed, you can install it by using
Selective Install and selecting Advanced Power
Management. For information about Selective
Install, see "Selective Install".
Note: This power management feature is not
available if your computer does not have
APM BIOS or a device driver that emulates
APM BIOS.
OS/2 2.1 APM support relies on the power status
information returned from the BIOS on your
computer. You might notice incorrect battery life
or status within the Power icon on your computer.
If this occurs, rely on the LEDs on your computer
for accurate power status information.
Turning the APM setting to Off also turns off the
BIOS power management. If you want to turn off
APM, but not the BIOS power management, place REM
before the APM device driver statement in your
CONFIG.SYS file, and then restart your system to
invoke the change.
For example:
REM DEVICE=C:\OS2\APM.SYS
Power Object
To open the Power object:
1. Open OS/2 System.
2. Open System Setup.
3. Open Power.
To display the Power pop-up menu:
1. Point to the Power object.
2. Click mouse button 1 or 2.
Power Settings
To set power management support:
1. Display the Power object pop-up
menu.
2. Select the arrow to the right of
Open.
3. Select Settings. The Power -
Settings notebook appears.
4. Select Power.
5. Set Power management to On or
Off. If set to On, power
consumption will be reduced and
power status will be tracked.
If set to Off, the suspend mode,
power status, and battery status
features are disabled.
6. Set Confirm on power state
changes if you want to confirm
requests to go to suspend mode.
(See "Suspend Mode.")
To set the default status view of
the status window:
1. Display the Power object pop-up
menu.
2. Select the arrow to the right of
Open.
3. Select Settings. The Power -
Settings notebook appears.
4. Select View.
5. Select Full status or Battery
only for Default status view.
6. Set Refresh (of the status
window) to On or Off.
7. If you set Refresh to On, select
the number of minutes (from 1 to
30) for Refresh rate. The
system will automatically update
the status window at the
intervals you specified.
You can also update the status
window by selecting Refresh Now
from the Power object pop-up
menu.
Power Status
To display the power status:
1. Display the Power object pop-up
menu.
2. Select the arrow to the right of
Open.
3. Select Full status or Battery
status. A full-status Power
window or a power-gauge Power
window is displayed, depending
on your selection.
Note: You cannot change the size of
the Power window.
A full-status Power window displays the following
information:
o Battery life. This information is displayed
as a power gauge that shows the power level of
the battery compared to the capacity of the
battery. When the power gauge indicator is
completely shaded, the battery is at full
power. The shaded area of the gauge moves up
or down as the battery power level increases
or decreases. When the power gauge indicator
is dimmed, there is no battery in the computer
or the computer cannot provide battery
information.
o Power source for the computer. If the system
cannot determine the power source, no power
source information is displayed.
o Battery state, which is the charge state of
the battery. Battery state information is
displayed as follows:
High Battery charge is OK; continue
using your computer.
Low Recharge the battery or switch to
another power source such as
another battery or AC power.
Critical Battery charge is depleted.
Recharge the battery or switch to
another power source immediately
to avoid a system failure or data
loss.
Charging System is restoring the battery
charge.
Unknown System cannot determine the
battery state or there is no
battery in your computer.
Suspend Mode
To set the suspend mode:
1. Display the Power object pop-up
menu.
2. Select Suspend.
When suspend mode is activated, battery power is
conserved by dimming the display and turning off
devices that are not in use.
If Confirm on power status changes is set in the
Power - Settings notebook, a message that asks you
if you want to continue is displayed before
switching to suspend mode.
Note: Different computers have different
procedures for exiting suspend mode and
resuming operation. Refer to the
documentation that came with your computer
for information about its suspend mode
features.
After you exit suspend mode, you will
notice a startup delay before you can
resume operation of your system. This
delay might be a few seconds, depending on
your system.
PCMCIA
OS/2 2.1 provides software support for Personal
Computer Memory Card International Association
(PCMCIA) hardware. PCMCIA(**) is the standard for
PC card adapters associated with portable
computers. A PC card is a small form-factor
adapter about the size and shape of a credit card.
You can use PC cards with laptops, notebooks,
tablets, and other portable computer systems that
are equipped with a PCMCIA slot.
To install PCMCIA, use Selective Install and
select PCMCIA. For information about Selective
Install, see "Selective Install".
CHAPTER 5. STARTUP
___________________
> On page 93, replace all text after the first
paragraph with the following:
If you add hard disk drives or partitions
after the installation of the OS/2 operating
system, you should edit the CONFIG.SYS file
and update the AC:x parameter to reflect the
new additions. AC: starts the auto-check
feature on the specified drives when the
system shuts down improperly. The value x
represents the letters of the disks or
partitions on the system that you want to
check.
For example, if you want to check disks C and
D and your existing DISKCACHE statement is:
DISKCACHE=64,LW
Add the AC: parameter to the statement as
follows:
DISKCACHE=64,LW,AC:CD
CHAPTER 6. DRIVES
__________________
> On page 95, add the following note before the
section titled "About Hard Disks and
Diskettes":
Note: Drive objects cannot be copied.
> On page 97, add the following note to the Tree
view paragraph:
Note: When an additional folder is opened
from a folder that is in tree view, if
the default for the additional folder
is also tree view, it is overridden and
displayed in an icon view. There is no
need to open it again in tree view
because it is already shown in the
parent folder's tree view.
---------------
(**) PCMCIA is a trademark of Personal Computer Memory Card International
Association.
> On page 101, replace the instructions in the
section titled "Moving Objects" with the
following:
To move an object from a drive to
another location:
1. Open the drive containing the
object you want to move.
2. Point to the object you want to
move.
3. Press and hold mouse button 2.
4. Drag the object to a folder, the
desktop, or another drive
object.
5. Release mouse button 2.
> On page 102, replace the moving instructions
with the following:
To move an object from another
location to a drive:
1. Point to the object you want to
move.
2. Press and hold mouse button 2.
3. Drag the mouse to the drive
object.
4. Release mouse button 2.
> On page 109, replace instruction #16 with the
following:
16. Type the following information into
the data file:
DEVICE=FSFILTER.SYS
DEVICE=C:\OS2\MDOS\HIMEM.SYS
DEVICE=C:\OS2\MDOS\EMM386.SYS
DOS=HIGH,UMB
DEVICEHIGH=C:\OS2\MDOS\ANSI.SYS
FILES=20
BUFFERS=20
CHAPTER 8. PRODUCTIVITY
________________________
> On page 117, add the following note to the
section titled "Picture Viewer":
Note: Picture Viewer does not support
multiple-page metafiles.
CHAPTER 10. INFORMATION
________________________
> On page 133, replace line 3 of the
instructions in the section titled "Printing
the README" with the following:
3. Drag the README object to a printer object.
CHAPTER 12. DRIVE A
____________________
> On page 139, add the following note before the
section titled "Display the Objects on a
Diskette":
Note: The Drive A object cannot be copied.
> On page 141, replace all the instructions
following the note in the section titled
"Copying Objects to or from a Diskette" with
the following:
To copy an object from a diskette in
Drive A to another location:
1. Place a diskette into drive A.
2. Open Drive A.
3. Point to the object you want to
copy.
4. Press and hold Ctrl.
5. Press and hold mouse button 2.
6. Drag the object to a folder, the
desktop, or another drive
object.
7. Release mouse button 2.
8. Release Ctrl.
To copy an object from another
location to a diskette in Drive A:
1. Place the diskette you want to
copy the object to into drive A.
2. Point to the object you want to
copy.
3. Press and hold Ctrl.
4. Press and hold mouse button 2.
5. Drag the mouse to the Drive A
object.
6. Release mouse button 2.
7. Release Ctrl.
> On page 142, replace all the instructions
following the note in the section titled
"Moving Objects to or from a Diskette" with
the following:
To move an object from the diskette
in Drive A to another location:
1. Place a diskette into drive A.
2. Open Drive A.
3. Point to the object you want to
move.
4. Press and hold Shift.
5. Press and hold mouse button 2.
6. Drag the object to a folder, the
desktop, or another drive
object.
7. Release mouse button 2.
8. Release Shift.
Note: When moving an object from a diskette,
the Shift key must be used with mouse
button 2.
To move an object from another
location to the diskette in Drive A:
1. Place the diskette you want to
move the object to into drive A.
2. Point to the object you want to
move.
3. Press and hold Shift.
4. Press and hold mouse button 2.
5. Drag the object to the Drive A
object.
6. Release mouse button 2.
7. Release Shift.
Note: When moving an object to a diskette,
the Shift key must be used with mouse
button 2.
CHAPTER 16. PRINTERS AND PLOTTERS
__________________________________
> On page 166, add the following instruction
between lines 7 and 8:
7a. Select Install new printer
driver.
CHAPTER 17. PREPARING YOUR PROGRAMS
____________________________________
> On page 185, add the following note before the
section titled "Viewing Program Object
Settings":
Note: The PgUp and PgDn keys on the numeric
keypad should not be used to move
between pages.
CHAPTER 18. USING WINDOWS PROGRAMS
___________________________________
> On page 196, replace the last sentence in the
section titled "Character Map" with the
following:
Character Map works with Windows and OS/2
programs.
> On page 199, replace all the text after the
first paragraph in the section titled
"Locating Window Programs" with the following:
When you run the Migrate Applications program for existing
Windows programs, the WIN-OS/2 Groups folder is created
and placed on the desktop. The WIN-OS/2 Groups folder
contains folders of Windows application programs that
reside in the default groups, WIN-OS/2 Accessories and
WIN-OS/2 Main. A group is a set of Windows programs that
are related.
The Windows Programs folder contains Windows programs that
have settings preselected to optimize the performance of
your program. Windows programs that do not belong to any
group are migrated to the Windows Programs folder.
The Additional Windows Programs folder contains Windows
programs that have default settings for your programs.
(If these programs do not run correctly, you can specify
other settings.)
For example, if you have CorelDraw(**) for
Windows installed, when you run the Migrate
Applications program, a folder for all the
CorelDraw programs is created and placed in
the Additional Window Programs folder. Now
you have access to all the CorelDraw programs
in one folder. For more information about
migrating programs, see "Migrate
Applications".
> On page 201, replace the paragraph at the top
of the page with the following:
When you change the value of a setting before
you start a session, the changes affect all
programs running in that session. When you
change the value of a setting while the
session is running, the changes will not have
any effect until you restart the session. If
you want the changes to remain whenever you
start a specific session or program, you must
save the changes.
> On page 201, add the following note before the
section titled "Running Window Programs in
WIN-OS/2 Sessions":
Note: The changes will not take effect until
you restart the session.
> On page 202, replace the last sentence with
the following:
To run more than one Windows program, repeat
the above steps as needed.
> On page 205, replace the last paragraph before
the section titled "Using the Clipboard and
Dynamic Data Exchange Features" with the
following:
To switch between active WIN-OS/2 sessions,
press Alt+Tab.
CHAPTER 23. AUDIO SUPPORT FOR APPLICATIONS
___________________________________________
> On page 259, move the sentence that reads "If
there are cells that have audio, each of these
cells is shown, one by one, as selected and
unshaded." to the end of the page.
> On page 260, move the first paragraph
beginning with "If the cell you select..." to
after the delete instructions. Move the
paragraph beginning with "If the work sheet is
not synchronized..." to after the second set
of instructions.
PART 5: EXTRA HELP
___________________
> On page 263, replace the entry list with the
following:
o What to do when you have a problem
o Tuning the performance of your system
o Software support, including information
about the OS/2 clipboard and Dynamic Data
Exchange (DDE)
o Video support, including information about
Super VGA, XGA(*) systems, and laptop LCD
displays
o Printing support, including information
about installing and configuring printer
drivers
o Hardware support, including information
about high-resolution displays, CD-ROM
drives, Advanced Power Management (APM),
and mobile computing
CHAPTER 24. SOLVING PROBLEMS
_____________________________
> On page 267, replace the sentence in the first
Action column that begins "Refer to 'Adding
online documentation...'" with the following:
Refer to "documentation, adding after
installation" in the Master Help Index.
> On page 273, replace the first paragraph in
the Action column with the following:
Download the program and try to run it without
the network. If the program runs, the problem
is probably related to the network. Ask your
network administrator for assistance.
> On page 282, replace the DOS setting
"MOUSE_EXCLUSIVE_ACCESS DOS setting" in the
Action column with the following:
MOUSE_EXCLUSIVE_ACCESS
> On page 285, replace the example beginning
with "MODE COM3 ..." in the Action column
with the following:
MODE COM3 IDSR=OFF ODSR=OFF OCTS=OFF
> On page 285, replace the paragraph beginning
with "Fax programs must..." in the Action
column with the following:
DOS fax programs must operate at less than
9600 bps. Use an OS/2 fax program for
high-speed faxing.
CHAPTER 26. SOFTWARE SUPPORT
_____________________________
> On page 301, delete the first sentence under
Enhanced Editor.
> On page 301, add the following section after
Enhanced Editor:
ES 1.0 Database Manager
o To properly install the ES 1.0 Database
Manager, the file ESSTART.BAK must be
copied from the OS/2 2.1 Installation
Diskette to the ES 1.0 installation
diskette and renamed ESSTART.CMD.
> On page 309, replace the statement beginning
with "123MEMSIZE=2048 ..." with the following:
SET 123MEMSIZE=2048
CHAPTER 27. VIDEO SUPPORT
__________________________
> On page 334, replace the statement "UNPACK
A:G.FON" with the following:
UNPACK A:*G.FON
CHAPTER 28. PRINTER SUPPORT
____________________________
> On page 353, add the following Lexmark(**)
bulletin board phone number to the end of the
first sentence in the section titled "IBM 4019
and IBM 4029 Printers":
(1-606-232-5238)
CHAPTER 29. HARDWARE SUPPORT
_____________________________
> On page 363, replace the last entry under the
Model column with the following:
CR-501, LK-MC501S, MC501B
> On page 366, replace the first paragraph in
the Comments column with the following:
IBM SCSI and Future Domain 16-bit SCSI
adapters might work, but are not supported by
IBM.
> On page 373, each BASEDEV example should
contain all of its parameters on one line.
> On page 378, replace the example beginning
with "DEVICE=X ..." with the following:
DEVICE=X:\OS2\COM.SYS (n,a,i,s)
> On page 383, add the following section:
Advanced Power Management Support for Laptop
Computers
Laptop computers with the following are
compatible with OS/2 2.11 Advanced Power
Management:
o 16-bit protect-mode APM in BIOS
o 32-bit protect-mode APM in BIOS
Laptop computers that have no APM support in
BIOS or have only real-mode APM are not
supported by OS/2 2.11 Advanced Power
Management.
The DOS utility program APMHERE, which is
available on the IBM BBS, can quickly
determine whether your machine has Advanced
Power Management support in conformance to the
APM 1.0 Specification (dated 1/91). Systems
with BIOS dates prior to January 1991 will not
have the protect-mode APM support in their
BIOS.
Laptop Computers with APM Support
The table that follows lists the laptop
computers that have Advanced Power Management
support. (This list represents only systems
tested as of January 27, 1994.)
---------------
(**) CorelDraw is a trademark of Corel Systems Corporation.
(*) Trademark of the IBM Corporation.
(**) Trademark of Lexmark International, Inc.
+------------------+--------------+--------------+
| Manufacturer | Model | Comments |
+------------------+--------------+--------------+
| Acer America | AcerNote 730 | BIOS |
| Corp. | | information |
| | | displayed on |
| | | start up: |
| | | |
| | | PhoenixBIOS|TM) A486
| | | Version 1.0| R1.0
+------------------+--------------+--------------+
| Acer America | AcerNote 750 | |
| Corp. | | |
+------------------+--------------+--------------+
| AST Research, | PowerExec | |
| Inc. | 4/25SL | |
+------------------+--------------+--------------+
| AST Research, | PowerExec | Perform the |
| Inc. | 4/25SL Color | following |
| | Plus | steps: |
| | 486SL/25 | |
| | Active | 1. Press FN |
| | Matrix Color | F1 keys |
| | | to get |
| | | BIO |
| | | access |
| | | 2. Select |
| | | Power |
| | | Managemen|
| | | 3. Click on |
| | | Power |
| | | Managemen|
| | | Section |
| | | 4. Follow |
| | | the |
| | | Character|ze
| | | the |
| | | Battery |
| | | instructi|ns
+------------------+--------------+--------------+
| Compaq Computer | 4/25 | |
| Corp. | | |
+------------------+--------------+--------------+
| Compaq Computer | CONTURA 4/25 | |
| Corp. | Monochrome, | |
| | VGA | |
+------------------+--------------+--------------+
| Compaq Computer | CONTURA | |
| Corp. | 4/25C | |
| | 486SL/25 | |
| | Active | |
| | Matrix | |
+------------------+--------------+--------------+
| Compaq Computer | CONTURA | See Note 1. |
| Corp. | 4/25cx | |
+------------------+--------------+--------------+
| Compudyne | 4SL/25 | BIOS |
| | SubNOTEBOOK | information |
| | | displayed on |
| | | start up: |
| | | |
| | | PhoenixBIOS|TM) LAP486SL
| | | Version 1.0|
| | | PhoenixMISE|(TM) 486L v2.0
| | | 80486SL BIO|
| | | Version 1.1| 5/28/93
+------------------+--------------+--------------+
| Gateway 2000, | ColorBook | |
| Inc. | 486SX/25 | |
| | 486SX/25 | |
| | Dual Scan | |
| | Color | |
+------------------+--------------+--------------+
| Gateway 2000, | ColorBook | See Note 1. |
| Inc. | 486DX/33 | Requires |
| | 486DX/33 | corrected |
| | Dual Scan | BIOS from |
| | Color | System Soft, |
| | | Inc.; see |
| | | Note 2. |
+------------------+--------------+--------------+
| Gateway 2000, | HandBook | See Note 1. |
| Inc. | 486DX2/40 | Requires |
| | 486DX2/40 | corrected |
| | Monochrome | BIOS from |
| | | System Soft, |
| | | Inc.; see |
| | | Note 2. |
+------------------+--------------+--------------+
| IBM Corporation | P/S NOTE | For OS/2 |
| | 425, 425c | 2.11, use F1 |
| | | to display |
| | | the |
| | | configuration|
| | | panel and |
| | | set Resume |
| | | on Alarm to |
| | | OFF when |
| | | running the |
| | | Alarm |
| | | applet. |
+------------------+--------------+--------------+
| IBM Corporation | ThinkPad | Version 1.2 |
| | 700, 700C, | of the |
| | 720, 720C, | reference |
| | 750 | and |
| | | diagnostic |
| | | diskettes |
| | | are |
| | | required. |
+------------------+--------------+--------------+
| NCR Corporation | NCR(**) 3150 | BIOS |
| | 486SX/25 | information |
| | Active | displayed on |
| | Matrix Color | start up: |
| | | |
| | | PhoenixBIOS|TM) A486
| | | Version 1.0|
| | | (C)1989-199|
| | | Phoenix Tec|nologies Ltd.
| | | All Rights |eserved.
| | | Reference I| 15
+------------------+--------------+--------------+
| NCR Corporation | SAFARI | Battery |
| | | Life, Power |
| | | Source, and |
| | | Battery |
| | | State |
| | | information |
| | | is |
| | | incorrect. |
+------------------+--------------+--------------+
| NEC Corporation | UltraLite | |
| | Versa | |
+------------------+--------------+--------------+
| Sharp | 6800 | Battery |
| | | Life, Power |
| | | Source, and |
| | | Battery |
| | | State |
| | | information |
| | | might be |
| | | incorrect. |
+------------------+--------------+--------------+
| Texas | TravelMate(**| |
| Instruments, | 4000, | |
| Inc. | 486DX2, | |
| | 50MHz | |
+------------------+--------------+--------------+
| Toshiba | T1950, | |
| Corporation | T1950CS, | |
| | T1950CT | |
| | 486DX2/40 | |
| | Mono, Dual | |
| | Scan Color, | |
| | Active | |
| | Matrix Color | |
+------------------+--------------+--------------+
| Toshiba | T3400, | |
| Corporation | T3400CT | |
| | 486SX/33 | |
| | Monochrome, | |
| | Active | |
| | Matrix Color | |
+------------------+--------------+--------------+
| Toshiba | T4700CS | |
| Corporation | 486DX2/50 | |
| | Dual Scan | |
| | Color | |
+------------------+--------------+--------------+
| Toshiba | T4700CT | |
| Corporation | 486DX2/50 | |
| | Active | |
| | Matrix Color | |
+------------------+--------------+--------------+
| Toshiba | T6600C, | |
| Corporation | T6600C/CD, | |
| | T6600C/CDV | |
| | 486DX2/66 | |
| | Active | |
| | Matrix Color | |
+------------------+--------------+--------------+
| Twinhead Corp. | SubNote | Does not |
| | 486DX/33 | have the CPU |
| | 486DX/33 | clock |
| | Monochrome | slowdown |
| | | feature; see |
| | | Note 3. |
+------------------+--------------+--------------+
| Zenith | MastersPort | |
| Electronics | 386SLe | |
| Corp. | | |
+------------------+--------------+--------------+
| Zenith | ZNOTE 325L | |
| Electronics | | |
| Corp. | | |
+------------------+--------------+--------------+
Note 1: To run OS/2 2.11 in these models,
change the "BASEDEV=IBM1S506.ADD"
statement in CONFIG.SYS to the
following:
BASEDEV=IBMINT13.I13
Note 2: For these models, the following BIOS
information is displayed on start up:
Systems Soft Bios for 80486/82C463 v1.01 (2069-09)
Contact Systems Soft, Inc.
(508-651-0088) for a corrected version
of BIOS.
Note 3: The OS/2 APM calls the BIOS APM once
per second to check if it is OK to do a
suspend. The following BIOS do not
return OK to suspend if the video
display is active or changes during the
CMOS suspend timeout:
o PhoenixBIOS Version 1.03
o Phoenix NoteBIOS 486/OPTi463
Version 1.03
o PhoenixMISER V2.0
Laptop Computers without APM Support
The table that follows lists the laptop
computers that do not have APM support in
their BIOS; however, they can be configured to
run OS/2 2.11 if APM is not installed. (This
list represents only systems tested as of
January 27, 1994.)
If you have installed OS/2 APM, ensure that it
is removed properly by doing the following:
o Remove the following two APM device
statements from CONFIG.SYS:
DEVICE=C:\OS2\APM.SYS
DEVICE=C:\OS2\MDOS\VAPM.SYS
o Delete the APM.SYS and VAPM.SYS files from
the corresponding hard-disk
subdirectories. This gains about 1 second
in startup and frees up hard-disk space.
+------------------+--------------+--------------+
| Manufacturer | Model | Comments |
+------------------+--------------+--------------+
| Compaq Computer | LTE-386s/25 | See Note 1. |
| Corp. | | |
+------------------+--------------+--------------+
| Compaq Computer | LTE LITE | See Note 1. |
| Corp. | 25/c 386SL | |
+------------------+--------------+--------------+
| Compaq Computer | LTE LITE | See Note 1. |
| Corp. | 4/25e, | |
| | 4/25c, | |
| | 486SL/25 | |
| | Active | |
| | Matrix | |
+------------------+--------------+--------------+
| Compudyne | 3SXL/25 | BIOS |
| | SLIMNOTE | information |
| | | displayed on |
| | | start up: |
| | | |
| | | PhoenixBIOS|TM) for
| | | VLSI Laptop|80386 BIOS
| | | Version 1.0| R2-1 06/09/92
+------------------+--------------+--------------+
| IBM Corporation | L40SX | Discontinued |
| | | product. |
| | | See Note 2. |
+------------------+--------------+--------------+
| IBM Corporation | P/S NOTE, | For OS/2 |
| | Model 2141 | 2.11, use F1 |
| | | to get the |
| | | configuration|
| | | panel and |
| | | set Resume |
| | | on Ring and |
| | | Resume on |
| | | Alarm to |
| | | OFF. |
+------------------+--------------+--------------+
| IBM Corporation | PS/2 N51 | Install |
| | 386SX/SLC | using |
| | 8551-025 | UINSTALL. |
+------------------+--------------+--------------+
| Librex | T386SX | If screen is |
| | | black after |
| | | resume, |
| | | toggle the |
| | | F1 key |
| | | (Suspend |
| | | key) to |
| | | refresh |
| | | screen. |
+------------------+--------------+--------------+
| Northgate | ZX Portable | BIOS |
| Computer Systems | 486SX/25 | information |
| | | displayed on |
| | | start up: |
| | | |
| | | Phoenix A48| version 1.01
| | | |
| | | See Note 3. |
+------------------+--------------+--------------+
| Texas | TravelMate | See Note 3. |
| Instruments, | 4000 WinDX2, | |
| Inc. | 486DX/25 MHz | |
+------------------+--------------+--------------+
| Texas | TravelMate | See Note 3. |
| Instruments, | 4000 | |
| Inc. | WinSX(**) | |
+------------------+--------------+--------------+
| Texas | TravelMate | See Note 3. |
| Instruments, | 4000e SX25 | |
| Inc. | Passive | |
| | Matrix Color | |
+------------------+--------------+--------------+
| Texas | TravelMate | See Note 3. |
| Instruments, | 4000e | |
| Inc. | WinDX2/50 | |
| | Active Color | |
+------------------+--------------+--------------+
| Texas | TravelMate | See Note 3. |
| Instruments, | 4000 | |
| Inc. | WinDX2/50 | |
| | 486DX2/50 | |
| | Monochrome | |
+------------------+--------------+--------------+
| Toshiba | T1800 | See Note 4. |
| Corporation | 386SX/20 | |
| | Monochrome | |
+------------------+--------------+--------------+
| Toshiba | T1850, | See Note 4. |
| Corporation | T1850C | |
| | 386SX/25 | |
| | Monochrome, | |
| | Dual Scan | |
| | Color | |
+------------------+--------------+--------------+
| Toshiba | T1900, | See Note 4. |
| Corporation | T1900C | |
| | 486SX/20 | |
| | Monochrome, | |
| | Dual Scan | |
| | color | |
+------------------+--------------+--------------+
| Toshiba | T2200SX | See Note 4. |
| Corporation | 386SX/20 | |
| | Monochrome | |
+------------------+--------------+--------------+
| Toshiba | T3100SX | See Note 4. |
| Corporation | 386SX/16 | |
| | Mono Plasma | |
+------------------+--------------+--------------+
| Toshiba | T3300SL | See Note 5. |
| Corporation | 386SL/20 | |
| | Monochrome | |
+------------------+--------------+--------------+
| Toshiba | T4400SX, | See Note 4. |
| Corporation | T4400SXP, | |
| | T4400SXC | |
| | 486SX/25 | |
| | Mono, | |
| | Plasma, | |
| | Active | |
| | Matrix Color | |
+------------------+--------------+--------------+
| Toshiba | T4400C | See Note 4. |
| Corporation | 486DX/33 | |
| | Active | |
| | Matrix Color | |
+------------------+--------------+--------------+
| Toshiba | T4500, | See Note 4. |
| Corporation | T4500C | |
| | 486SX/20 | |
| | Monochrome, | |
| | Active | |
| | Matrix Color | |
+------------------+--------------+--------------+
| Toshiba | T4600, | See Note 5. |
| Corporation | T4600C | |
| | 486SL/33 | |
| | Monochrome, | |
| | Active | |
| | Matrix Color | |
+------------------+--------------+--------------+
Note 1: To run OS/2 2.11 in these models,
change the "BASEDEV=IBM1S506.ADD"
statement in CONFIG.SYS to the
following:
BASEDEV=IBMINT13.I13
Note 2: For OS/2 2.11 APM, access the IBM BBS
and download the following 3 files:
o TGSFX.COM (located in file area 4)
o RFL40SXA.TG0 (located in file area
27)
o L40PWR.ZIP (located in file area
37)
---------------
(**) NCR is a trademark of the NCR Corporation. TravelMate is a trademark of
Texas Instruments, Inc.
(**) WinSX is a trademark of Texas Instruments, Inc.
Execute TGSFX.COM to install the
TELEGET.EXE program. Then do the
following:
1. Create a new L40SX reference
diskette by using TELEGET.EXE to
unpack RFL40SXA.TG0 onto a 1.44MB
formatted diskette.
2. Use PKUNZIP to unzip the L40PWR.ZIP
to obtain new IDLE.EXE and
PWRMGMT.SYS files.
3. Replace the IDLE.EXE and
PWRMGMT.SYS files on the newly
created L40SX reference diskette
with the new IDLE.EXE and
PWRMGMT.SYS files obtained from the
previous step.
4. Restart L40SX with the resulting
reference diskette in A drive and
configure with APM.
5. Verify the APM configuration by
selecting VIEW configuration from
the installation menu.
6. Exit the configuration.
7. Power off the computer and restart
OS/2.
Note 3: Contact the manufacturer for newer
versions of their BIOS that have APM
support.
Note 4: These models require the Toshiba APM
driver (OS2RES.EXE) available from the
Toshiba BBS (714-837-4408). This
driver will provide partial power
management capabilities under OS/2
2.11.
Note 5: While running OS/2, you can use the
special power-saving keys but the
additional capability of OS/2
protect-mode APM is not supported.
APPENDIX B. ERROR MESSAGES
___________________________
> On page 422, replace the paragraph under
Action: for the SYS0206E message with the
following:
Correct the file name or the extension; then
retry the command. For more information about
file names, refer to "types of files,
description" in the Master Index.
APPENDIX C. BACKING UP AND RESTORING YOUR DESKTOP
__________________________________________________
> On page 431, replace the last note with the
following:
Note: The name of your DESKTOP directory
might be slightly different if you use
HPFS or if you previously replaced your
desktop. To find the actual name of
your DESKTOP directory currently in
use, display the Settings notebook for
the desktop and select the File page.
The current desktop name is shown under
Physical name.
> On page 431, replace the last line with the
following:
BACKUP C:\OS2\DESKTOP A: /S
> On page 433, replace lines #10, #11, and #12
with the following instructions:
10. Delete the existing desktop directory
and its subdirectories.
11. Use the RESTORE command to copy the
DESKTOP directory and its subdirectories
from the diskette to the hard drive.
RESTORE A: C:\OS2\DESKTOP /S
This will ensure that the desktop folders
are displayed correctly.
12. Remove the diskette from drive A.
13. Press Ctrl+Alt+Del to restart the
computer.
APPENDIX F. REMOVING PROGRAMS
______________________________
> On page 453, replace the bit-map paths with
the following:
\OS2\BITMAP\BLOCKS.BMP
\OS2\BITMAP\BOX.BMP
\OS2\BITMAP\BRICK.BMP
\OS2\BITMAP\BUTTERFL.BMP
\OS2\BITMAP\COLUMNS.BMP
\OS2\BITMAP\DELFT.BMP
\OS2\BITMAP\FLAMINGO.BMP
\OS2\BITMAP\FLEUR.BMP
\OS2\BITMAP\LEAVES.BMP
\OS2\BITMAP\LINES.BMP
\OS2\BITMAP\LINKS.BMP
\OS2\BITMAP\MAZE.BMP
\OS2\BITMAP\MERCADO.BMP
\OS2\BITMAP\ORCHIDS.BMP
\OS2\BITMAP\ROOF.BMP
\OS2\BITMAP\SCALES1.BMP
\OS2\BITMAP\SCALES2.BMP
\OS2\BITMAP\SHELL.BMP
\OS2\BITMAP\SPIRAL.BMP
\OS2\BITMAP\STARS.BMP
\OS2\BITMAP\TILE.BMP
\OS2\BITMAP\TOOTH.BMP
\OS2\BITMAP\WAVE.BMP
\OS2\BITMAP\WEBB.BMP
\OS2\BITMAP\ZIGZAG.BMP
> On page 455, replace the RIPL .HLP path with
the following:
\OS2\INSTALL\RIPLINST.HLP
> On page 455, replace the TUTORIAL.HLP path
with the following:
\OS2\HELP\TUTORIAL\TUTORIAL.HLP
> On page 456, replace the KLONBGA.DLL path with
the following:
\OS2\APPS\DLL\KLONBGA.DLL
> On page 456, replace the NEKO.DLL path with
the following:
\OS2\APPS\DLL\NEKO.DLL
> On page 458, replace the PMSEEK.DLL path with
the following:
\OS2\APPS\DLL\PMSEEK.DLL
> On page 458, replace the .DLL paths for
Scramble with the following:
\OS2\APPS\DLL\SCRAMBLE.DLL
\OS2\APPS\DLL\SCRCATS.DLL
\OS2\APPS\DLL\SCRLOGO.DLL
> Starting on page 458, replace the .DLL paths
for SoftTerm with the following:
\OS2\APPS\DLL\CTLSACDI.DLL
\OS2\APPS\DLL\OACDISIO.DLL
\OS2\APPS\DLL\OANSI.DLL
\OS2\APPS\DLL\OANSI364.DLL
\OS2\APPS\DLL\OCHAR.DLL
\OS2\APPS\DLL\OCM.DLL
\OS2\APPS\DLL\OCOLOR.DLL
\OS2\APPS\DLL\OCSHELL.DLL
\OS2\APPS\DLL\ODBM.DLL
\OS2\APPS\DLL\OFMTC.DLL
\OS2\APPS\DLL\OIBM1X.DLL
\OS2\APPS\DLL\OIBM2X.DLL
\OS2\APPS\DLL\OKB.DLL
\OS2\APPS\DLL\OKBC.DLL
\OS2\APPS\DLL\OKERMIT.DLL
\OS2\APPS\DLL\OLPTIO.DLL
\OS2\APPS\DLL\OMCT.DLL
\OS2\APPS\DLL\OMRKCPY.DLL
\OS2\APPS\DLL\OPCF.DLL
\OS2\APPS\DLL\OPM.DLL
\OS2\APPS\DLL\OPROFILE.DLL
\OS2\APPS\DLL\ORSHELL.DLL
\OS2\APPS\DLL\OSCH.DLL
\OS2\APPS\DLL\OSIO.DLL
\OS2\APPS\DLL\OSOFT.DLL
\OS2\APPS\DLL\OTEK.DLL
\OS2\APPS\DLL\OTTY.DLL
\OS2\APPS\DLL\OVIO.DLL
\OS2\APPS\DLL\OVM.DLL
\OS2\APPS\DLL\OVT.DLL
\OS2\APPS\DLL\OXMODEM.DLL
\OS2\APPS\DLL\OXRM.DLL
\OS2\APPS\DLL\SACDI.DLL
\OS2\APPS\DLL\SAREXEC.DLL
Appendix A. Notices
References in this publication to IBM products,
programs, or services do not imply that IBM
intends to make these available in all countries
in which IBM operates. Any reference to an IBM
product, program or service is not intended to
state or imply that only IBM's product, program,
or service may be used. Any functionally
equivalent product, program, or service that does
not infringe any of IBM's intellectual property
rights or other legally protectable rights may be
used instead of the IBM product, program, or
service. Evaluation and verification of operation
in conjunction with other products, programs, or
services, except those expressly designated by
IBM, are the user's responsibility.
IBM may have patents or pending patent
applications covering subject matter in this
document. The furnishing of this document does
not give you any license to these patents. You
can send license inquiries, in writing, to the IBM
Director of Licensing, IBM Corporation, 208 Harbor
Drive, Stamford, Connecticut 06904-2501, USA.
TRADEMARKS AND SERVICE MARKS
____________________________
The following terms, denoted by an asterisk (*) in
this publication, are trademarks or service marks
of the IBM Corporation in the United States or
other countries:
AT IBM
Micro Channel OS/2
PS/1 PS/2
ThinkPad Ultimotion
WIN-OS/2 XGA
The following terms, denoted by a double asterisk
(**) in this publication, are trademarks of other
companies as follows:
Trademark Owner
Adaptec Adaptec, Inc.
Allways Funk Software, Inc.
AMI American Megatrends, Inc.
ATI ATI Technologies, Inc.
Central Point Central Point Software,
Inc.
Compaq Compaq Computer
Corporation
CorelDraw Corel Systems Corporation
Docking Station NEC Home Electronics,
Inc.
Future Domain Future Domain Corporation
Gateway Gateway Systems
Corporation
Gateway 2000 Gateway 2000, Inc.
Hitachi Hitachi Ltd.
HYPERACE Hypertec Pty. Limited
Lexmark Lexmark International,
Inc.
McAfee McAfee Associates.
Media Vision Media Vision, Inc.
Micropolis Micropolis Corporation
Microsoft Microsoft Corporation
Mitsumi Mitsumi Denki Kabushki
Kaisha
MS Microsoft Corporation
MS-DOS Microsoft Corporation
NCR NCR Corporation
NetWare Novell, Inc.
Nomad Gateway 2000, Inc.
Panasonic Matsushita Electric
Industrial Co., Ltd.
PCMCIA Personal Computer Memory
Card International
Association
Phoenix Phoenix Technologies,
Ltd.
ProAudio Spectrum Media Vision, Inc.
ProComm Datastorm Technologies,
Inc.
Quantum Quantum Corporation
Sony Sony Corporation
Sound Blaster Creative Labs, Inc.
The Norton Antivirus Symantec Corporation
TravelMate Texas Instruments, Inc.
Ultra ATI Technologies, Inc.
VESA Video Electronics
Standards Association
Windows Microsoft Corporation
WinSX Texas Instruments, Inc.