OS/2 Shareware BBS: 27 Fixes20/27-Fixes20.zip/d21-04.zip/D21-04.ASC

Text File | 1993-08-23 | 8KB | 191 lines

The following information replaces "Configuring Your
WIN-OS/2 Desktop Appearance", from OS/2 2.1 Using the Operating
System, page 33.
Changes are indicated by a | to the left of the text.

  CONFIGURING YOUR WIN-OS/2 DESKTOP APPEARANCE

Select CONFIGURE WIN-OS/2 DESKTOP to indicate how you
want the WIN-OS/2 desktop to look.  You can install
WIN-OS/2 support with the standard interface provided by
OS/2 2.1.  You can make the WIN-OS/2 desktop look like an
existing version of Microsoft Windows if you currently
have it installed.  If you select this choice, you can
also choose to update your existing version of Microsoft
Windows to look like the WIN-OS/2 desktop whenever it
changes.  Finally, you can choose to preserve how the
WIN-OS/2 desktop currently looks if you have previously
installed WIN-OS/2 support.

o   If you select the INSTALL STANDARD WIN-OS/2 DESKTOP
    choice, the installation program creates a new set of
    system (INI) files for the WIN-OS/2 feature.  These
    files determine such things as which programs appear
    on the desktop and what colors are used for the
    desktop.  There is no relationship between these
    files and the files from any pre-existing Windows
    system you might have.

o   If you select the COPY WIN-OS/2 DESKTOP FROM EXISTING
    WINDOWS DESKTOP choice, the installation program
    copies the system files from your existing Windows
    system to your WIN-OS/2 directory.  Additional OS/2
    information is then added to these files.  An advan-
    tage to selecting this choice is that, after instal-
    lation, your WIN-OS/2 desktop will look like your
    familiar Windows desktop.  However, any changes that
    you make to the WIN-OS/2 desktop will not be made to
    the Windows desktop.

|   However, if you select the UPDATE WINDOWS DESKTOP
|   WHEN WIN-OS/2 DESKTOP IS MODIFIED choice, the instal-
|   lation program points to your Windows system files.

o   Select PRESERVE WIN-OS/2 DESKTOP CURRENTLY INSTALLED
    if you already have a previous version of WIN-OS/2
    support installed and you want your newly installed
    version to resemble the current version.



.********************************************************************

The following is a supplement to the OS/2 2.1 information.


PCMCIA SUPPORT FOR OS/2 2.1

   OS/2 2.1 supports the Level 2.0 Personal
   Computer Memory Card International Association
   (PCMCIA) specification for credit-card sized
   adapters such as memory, I/O devices, modems,
   and LAN adapters.  OS/2 2.1 can support
   environments that comply with layers 1, 2, and
   3 of the PCMCIA specification.  As a result,
   OS/2 2.1 contains the Card Services support
   that allows adapter manufacturers to write
   Client Device Drivers and system manufacturers
   to ship Socket Services.

   Following is a brief description of each of the
   PCMCIA layers:

   Card Services:

   OS/2 2.1 contains the PCMCIA Card Services
   layer of support.  The OS/2 Card Services
   support provides PCMCIA 2.00 Card Services
   conforming interfaces as a 16-bit inter-device
   driver communications (IDC) interface.  These
   interfaces are documented in Chapter 13 of the
   OS/2 DDK I/O Device Driver Reference Manual.
   The PCMCIA Card Services layer is responsible
   for managing system resources on behalf of the
   Client Device Drivers and the Socket Services
   layer.  Client Device Drivers must use the Card
   Services interfaces to obtain access and
   configuration support for the various PC Cards
   supported by the client.

   Client Device Drivers:

   Client Device Drivers are required to
   manipulate the PC Card and provide the
   application transparency for the card devices.
   Client Device Drivers use the OS/2 Card
   Services IDC interface to setup and release the
   various resources (such as IRQ, IO ports, and
   memory addresses) for PC Cards.  These Client
   Device Drivers are supplied by the adapter
   manufacturer.  Initialization details as well
   as Card_Insertion and Card_Removal event
   processing examples are provided in Chapter 13
   of the OS/2 DDK IO Device Driver Reference
   Manual.

   Resource Utility:

   A special Client Device Driver exists, which is
   usually provided by the PC manufacturer.  This
   special client is called the Resource Utility
   or Resource Client.  The Resource Utility is
   responsible for providing Card Services with a
   system-specific resource map for the personal
   computer.  The Resource Client does not own any
   PC Cards or devices and is only active during
   the PCMCIA subsystem initialization.  OS/2 Card
   Services is initialized using a generic default
   system resource map that might not utilize the
   current system's resources in an optimal
   manner.  Therefore, it is important that a
   system specific Resource Utility be provided by
   each system manufacturer with system model
   resource details.  Please consult Chapter 13 of
   the OS/2 DDK IO Device Driver Reference Manual
   for details on the OS/2 Card Services default
   resource map as well as the Resource Utility.

   Socket Services:

   The PCMCIA Socket Services layer has the
   responsibility of encapsulating the socket
   hardware controller details into the PCMCIA
   Socket Services interfaces.  The PCMCIA Socket
   Services layer might be implemented in either
   ROM BIOS or as a device driver.  OS/2 Card
   Services uses the PCMCIA Socket Services 2.00
   interfaces implemented in a 16-bit IDC
   interface.  Because no ROM BIOS implementations
   of Socket Services were available to test, OS/2
   2.1 supports only implementations built as OS/2
   Physical Device Drivers.

   For more details please see Chapter 13 of the
   OS/2 DDK IO Device Driver Reference Manual.

   In summary, OS/2 2.1 provides the PCMCIA Card
   Services layer.  There are other PCMCIA layers
   that are required in order to have a fully
   functioning PCMCIA configuration.  The Socket
   Services and Resource Utility should come with
   the system unit/adapter option and should be
   located on the Hardware Options Reference/Setup
   diskette along with installation instructions.
   The Client Device Drivers should be provided by
   the PC Card/Device manufacturer and should be
   located on the PC Card Reference/Setup diskette
   along with installation instructions.  It
   should be noted that some PC Cards do not come
   with any software support or hardware reference
   diskettes.  These PC Cards require that a third
   party program manage the PC Card.  When
   purchasing PC Cards, be sure its requirements
   are fully explained.

   IBM is aware of its customer's problems in
   obtaining these layers of support and is
   working with the PCMCIA manufacturers to
   resolve this situation.


.*********************************************************************

The following information updates the OS/2 2.1 Installation Guide:

OS/2 2.1 INSTALLATION GUIDE UPDATE

   Throughout the OS/2 2.1 Installation Guide,
   references are made to the amount of disk space
   needed to install any or all of the operating
   system.  These amounts do not include the disk
   space required by the SWAPPER.DAT file.  The
   SWAPPER.DAT file is used by the operating
   system to store memory pages it moves out of
   memory.  Depending on the amount of memory and
   the types of applications you plan to run, you
   might need up to 12MB of additional disk space.

   When planning for the installation of OS/2 2.1,
   estimate your disk requirements to be 12MB
   higher than those stated in the book.